From: Steven Rostedt <rostedt@goodmis.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: torvalds@linux-foundation.org, mingo@kernel.org,
linux-kernel@vger.kernel.org, douglas.raillard@arm.com,
tglx@linutronix.de, rcu@vger.kernel.org, kernel-team@fb.com
Subject: Re: [GIT PULL] Fix rcu_torture_read ftrace event
Date: Tue, 28 Mar 2023 18:26:00 -0400 [thread overview]
Message-ID: <20230328182600.32e672ed@gandalf.local.home> (raw)
In-Reply-To: <9f32a8e2-7fc3-427b-b1e2-238fe81ce97e@paulmck-laptop>
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
prev parent reply other threads:[~2023-03-28 22:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 17:48 Paul E. McKenney
2023-03-28 20:33 ` pr-tracker-bot
2023-03-28 22:26 ` Steven Rostedt [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230328182600.32e672ed@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=douglas.raillard@arm.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®