linux-kernel - Re: linux-next: duplicate patches in the tip 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: <20241209114524.a150aba86198e6f0fc9afcbc@linux-foundation.org>
Date: Mon, 9 Dec 2024 11:45:24 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>, Thomas Gleixner
 <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, "H. Peter Anvin"
 <hpa@...or.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
 Linux Next Mailing List <linux-next@...r.kernel.org>, surenb@...gle.com
Subject: Re: linux-next: duplicate patches in the tip tree

On Mon, 9 Dec 2024 12:08:42 +0100 Peter Zijlstra <peterz@...radead.org> wrote:

> On Mon, Dec 09, 2024 at 01:29:41PM +1100, Stephen Rothwell wrote:
> > Hi all,
> > 
> > The following commits are also in the mm tree as different commits
> > (but the same patches):
> > 
> >   96450ead1652 ("seqlock: add raw_seqcount_try_begin")
> >   eb449bd96954 ("mm: convert mm_lock_seq to a proper seqcount")
> > 
> > These are commits
> > 
> >   46dbe8ab1205 ("seqlock: add raw_seqcount_try_begin")
> >   5f0d64389e1f ("mm: convert mm_lock_seq to a proper seqcount")
> > 
> > from the mm-unstable branch of the mm tree.  The latter ones are already
> > causing conflicts.
> 
> Why is this in -mm ?

Because
https://lore.kernel.org/all/20241206225204.4008261-1-surenb@google.com/T/#u
needs it.

> I agreed with Suren I'd take them through
> tip/perf/core to go along with Andrii's uprobe patch that relies on
> them.