mbox series

[GIT,PULL] Fix rcu_torture_read ftrace event

Message ID 9f32a8e2-7fc3-427b-b1e2-238fe81ce97e@paulmck-laptop
State New
Headers
Series [GIT,PULL] Fix rcu_torture_read ftrace event |

Pull-request

git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git tags/urgent-rcu.2023.03.28a

Message

Paul E. McKenney March 28, 2023, 5:48 p.m. UTC 
  Hello, Linus,

This post-merge-window urgent pull request brings the rcu_torture_read
event trace into line with the new trace tools.  Without this commit,
users of those tools perceive a regression.

Just in case there is confusion, the plan is still for Joel Fernandes
and Boqun Feng to send the RCU pull request into the v6.4 merge window.
I will be doing my other pull requests for v6.4, and I will also be
handling the RCU pull request for the v6.5 merge window.

The following changes since commit fe15c26ee26efa11741a7b632e9f23b01aca4cc6:

  Linux 6.3-rc1 (2023-03-05 14:52:03 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git tags/urgent-rcu.2023.03.28a

for you to fetch changes up to d18a04157fc171fd48075e3dc96471bd3b87f0dd:

  rcu: Fix rcu_torture_read ftrace event (2023-03-22 14:05:24 -0700)

----------------------------------------------------------------
Urgent RCU pull request for v6.3

This commit brings the rcu_torture_read event trace into line with
the new trace tools by replacing this event trace's __field() with the
corresponding __array().  Without this commit, the new trace tools will
fail when presented wtih an rcu_torture_read event trace, which is a
regression from the viewpoint of trace tools users.

https://lore.kernel.org/all/20230320133650.5388a05e@gandalf.local.home/

----------------------------------------------------------------
Douglas Raillard (1):
      rcu: Fix rcu_torture_read ftrace event

 include/trace/events/rcu.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Comments

pr-tracker-bot@kernel.org March 28, 2023, 8:33 p.m. UTC | #1 
The pull request you sent on Tue, 28 Mar 2023 10:48:14 -0700:

> git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git tags/urgent-rcu.2023.03.28a

has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/fcd476ea6a888ef6e6627f4c21a2ea8cca3e9312

Thank you!
Steven Rostedt March 28, 2023, 10:26 p.m. UTC | #2 
On Tue, 28 Mar 2023 10:48:14 -0700
"Paul E. McKenney" <paulmck@kernel.org> wrote:

> ----------------------------------------------------------------
> Urgent RCU pull request for v6.3
> 
> This commit brings the rcu_torture_read event trace into line with
> the new trace tools by replacing this event trace's __field() with the
> corresponding __array().  Without this commit, the new trace tools will
> fail when presented wtih an rcu_torture_read event trace, which is a
> regression from the viewpoint of trace tools users.
> 
> https://lore.kernel.org/all/20230320133650.5388a05e@gandalf.local.home/

Thanks! I'll base my change on top of v6.3-rc5 as that will include this
pull request.

 https://patchwork.kernel.org/project/linux-trace-kernel/patch/20230309221302.642e82d9@gandalf.local.home/

Which the kernel robot flagged as causing a build error due to this RCU
issue ;-)

-- Steve