[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221018185936.GX5600@paulmck-ThinkPad-P17-Gen-1>
Date: Tue, 18 Oct 2022 11:59:36 -0700
From: "Paul E. McKenney" <paulmck@...nel.org>
To: John Ogness <john.ogness@...utronix.de>
Cc: rcu@...r.kernel.org, linux-kernel@...r.kernel.org,
kernel-team@...com, rostedt@...dmis.org, tglx@...utronix.de,
pmladek@...e.com, Frederic Weisbecker <frederic@...nel.org>
Subject: Re: [PATCH v2 rcu 0/8] NMI-safe SRCU reader API
On Tue, Oct 18, 2022 at 08:50:57PM +0206, John Ogness wrote:
> On 2022-10-18, "Paul E. McKenney" <paulmck@...nel.org> wrote:
> > Currently, I have this series on -rcu branch srcunmisafe.2022.10.03a,
> > with Frederic's patches on branch "dev". I will be producing a shiny
> > new branch with your fix and Frederic's debug later today, Pacific
> > Time. With luck, based on v6.1-rc1.
>
> Perfect!
>
> > I will be incorporating these commits from Frederic:
> >
> > 6558b914fc4e ("srcu: Warn when NMI-unsafe API is used in NMI")
> > 5dc788627109 ("srcu: Explain the reason behind the read side critical section on GP start")
> > 54a118fce487 ("srcu: Debug NMI safety even on archs that don't require it")
> >
> > Are there other patches I should be applying?
>
> Not that I am aware of.
And if you are in a hurry, the v6.0-rc1 stack is at srcunmisafe.2022.10.18a.
With luck, the v6.1-rc1 stack will be at srcunmisafe.2022.10.18b before
the day is over, Pacific Time.
Thanx, Paul
Powered by blists - more mailing lists