[GIT PULL] Fix rcu_torture_read ftrace event

[Paul E. McKenney]

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@xxxxxxxxxxxxxxxxxx/

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

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