From: Steven Rostedt <rostedt@goodmis.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: Re: [PATCH] tracing: Do not synchronize freeing of trigger filter on boot up
Date: Fri, 16 Dec 2022 06:08:10 -0500 [thread overview]
Message-ID: <20221216060810.4e541bc4@gandalf.local.home> (raw)
In-Reply-To: <20221216044022.GA2467686@paulmck-ThinkPad-P17-Gen-1>
On Thu, 15 Dec 2022 20:40:22 -0800
"Paul E. McKenney" <paulmck@kernel.org> wrote:
> On Thu, Dec 15, 2022 at 05:01:18PM -0800, Paul E. McKenney wrote:
> > On Thu, Dec 15, 2022 at 06:42:02PM -0500, Steven Rostedt wrote:
> > > On Thu, 15 Dec 2022 15:10:27 -0800
> > > "Paul E. McKenney" <paulmck@kernel.org> wrote:
> > >
> > > > The nice thing about the current placement of rcu_scheduler_starting()
> > > > is that there is not yet any other task to switch to. ;-)
> > >
> > > Fair enough. Anyway the last patch appears to do the job.
> > >
> > > Reported-by: Steven Rostedt (Google) <rostedt@goodmis.org>
> > > Tested-by: Steven Rostedt (Google) <rostedt@goodmis.org>
> >
> > Applied, thank you!
>
> And I should have checked up on urgency. Normal process would hold this
> one until the v6.3 merge window, but please let me know if you would
> like it in v6.2. It is after all a bug fix.
>
Yes, any fix that fixes a lockdep splat is considered urgent and should be
pushed ASAP. As it makes finding other lockdep splats more difficult (as
the first splat shuts down lockdep).
Please send this during the merge window, as I have to carry it internally
until it makes it into mainline.
Thanks!
-- Steve
next prev parent reply other threads:[~2022-12-16 11:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 22:24 [PATCH] tracing: Do not synchronize freeing of trigger filter on boot up Steven Rostedt
2022-12-13 23:49 ` Masami Hiramatsu
2022-12-14 0:03 ` Steven Rostedt
2022-12-14 7:31 ` Masami Hiramatsu
2022-12-14 20:03 ` Paul E. McKenney
2022-12-14 20:37 ` Mathieu Desnoyers
2022-12-14 21:26 ` Paul E. McKenney
2022-12-15 15:02 ` Steven Rostedt
2022-12-15 17:02 ` Paul E. McKenney
2022-12-15 17:25 ` Paul E. McKenney
2022-12-15 18:51 ` Steven Rostedt
2022-12-15 19:01 ` Paul E. McKenney
2022-12-15 22:39 ` Steven Rostedt
2022-12-15 23:10 ` Paul E. McKenney
2022-12-15 23:42 ` Steven Rostedt
2022-12-16 1:01 ` Paul E. McKenney
2022-12-16 4:40 ` Paul E. McKenney
2022-12-16 11:08 ` Steven Rostedt [this message]
2022-12-18 0:29 ` Paul E. McKenney
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=20221216060810.4e541bc4@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=paulmck@kernel.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;
as well as URLs for NNTP newsgroup(s).