linux-kernel - Re: linux-next: duplicate patch in the rcu tree

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: <23c3ec9c-2b8d-4739-a7b4-f41c29f7d8d1@paulmck-laptop>
Date: Tue, 27 Feb 2024 17:20:34 -0800
From: "Paul E. McKenney" <paulmck@...nel.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patch in the rcu tree

On Wed, Feb 28, 2024 at 12:06:10PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> The following commit is also in the tip tree as a different commit
> (but the same patch):
> 
>   020eee167cca ("x86/nmi: Fix "in NMI handler" check")
> 
> This is commit
> 
>   d54e56f31a34 ("x86/nmi: Fix the inverse "in NMI handler" check")
> 
> in the tip tree.

Earlier today, I pulled it out of the range of -rcu patches that are
sent to -next.  If overnight testing goes well, you will not see the
copy from -rcu starting tomorrow.

Thank you for calling it out, though!

							Thanx, Paul