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]

Date: Wed, 28 Feb 2024 02:17:05 +0100
From: Thomas Gleixner <tglx@...utronix.de>
To: Stephen Rothwell <sfr@...b.auug.org.au>, "Paul E. McKenney"
 <paulmck@...nel.org>, Ingo Molnar <mingo@...hat.com>, "H. Peter Anvin"
 <hpa@...or.com>, Peter Zijlstra <peterz@...radead.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Next
 Mailing List <linux-next@...r.kernel.org>, x86@...nel.org
Subject: Re: linux-next: duplicate patch in the rcu tree

On Wed, Feb 28 2024 at 12:06, Stephen Rothwell wrote:
> 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.

And why the heck is the RCU tree carrying x86 specific stuff which has
absolutely nothing to do with RCU?

Just because, right?

Thanks,

        tglx