lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <370911ae-ce3c-4ebd-a348-452c73c06597@paulmck-laptop>
Date: Mon, 1 Dec 2025 16:57:54 -0800
From: "Paul E. McKenney" <paulmck@...nel.org>
To: Frederic Weisbecker <frederic@...nel.org>
Cc: Steven Rostedt <rostedt@...dmis.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	Neeraj Upadhyay <neeraj.upadhyay@...nel.org>,
	Boqun Feng <boqun.feng@...il.com>,
	Uladzislau Rezki <urezki@...il.com>,
	Masami Hiramatsu <mhiramat@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Next Mailing List <linux-next@...r.kernel.org>,
	Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Subject: Re: linux-next: manual merge of the rcu tree with the ftrace tree

On Tue, Nov 18, 2025 at 07:04:07AM -0800, Paul E. McKenney wrote:
> On Tue, Nov 18, 2025 at 02:05:03PM +0100, Frederic Weisbecker wrote:
> > Le Fri, Nov 14, 2025 at 09:06:29AM -0800, Paul E. McKenney a écrit :

[ . . . ]

> > > Thank you, Frederic, and I guess putting this in -next did indeed find
> > > some problems, so that is good?  ;-)
> > 
> > Indeed, mission accomplished ;-)
> > 
> > Steve proposed here to actually restore the patch:
> > 
> >     https://lore.kernel.org/lkml/20251114110136.3d36deca@gandalf.local.home/
> > 
> > But later said the reverse:
> > 
> >     https://lore.kernel.org/lkml/20251114121141.5e40428d@gandalf.local.home/
> > 
> > So for now I'm still keeping it outside -next. I hope it is not a necessary
> > change in your srcu series?
> 
> My thought is to put the patch with Steven's suggested removal on my
> -rcu stack and see what kernel test robot thinks of it.  ;-)

Unless I hear otherwise, I will push this into -next after the RCU
patches land.  If all goes well, I will send the pull request to Linus.
So please let me know if you would prefer some other course of action.

							Thanx, Paul

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ