Messages in this thread |  | | Date | Sat, 17 Dec 2022 16:29:03 -0800 | From | "Paul E. McKenney" <> | Subject | Re: [PATCH] tracing: Do not synchronize freeing of trigger filter on boot up |
| |
On Fri, Dec 16, 2022 at 06:08:10AM -0500, Steven Rostedt wrote: > 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.
This is now rebased and marked with tag rcu-urgent.2022.12.17a. If testing goes well, I will send it by the middle of next week.
Thanx, Paul
|  |