linux-kernel - Re: linux-next: manual merge of the char-misc.current tree with the mm-hotfixes 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: <20220819220243.ieq3drqvg3lcmark@revolver>
Date:   Fri, 19 Aug 2022 22:02:53 +0000
From:   Liam Howlett <liam.howlett@...cle.com>
To:     Andrew Morton <akpm@...ux-foundation.org>
CC:     Greg KH <greg@...ah.com>, Stephen Rothwell <sfr@...b.auug.org.au>,
        Arnd Bergmann <arnd@...db.de>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: manual merge of the char-misc.current tree with the
 mm-hotfixes tree

* Andrew Morton <akpm@...ux-foundation.org> [220819 16:35]:
> On Fri, 19 Aug 2022 13:35:04 +0000 Liam Howlett <liam.howlett@...cle.com> wrote:
> 
> > b3bb668f3dc6 is the older v1 of the patch [1]. d6f35446d076 from
> > mm-hotfixes is the correct v2 version [2], although I don't think that's
> > currently in mm-hotfixes-unstable.  It looks like version 1 is now in
> > mm-hotfixes-unstable as well.
> > 
> > 1: https://lore.kernel.org/linux-mm/20220809160618.1052539-1-Liam.Howlett@oracle.com/
> > 2: https://lore.kernel.org/linux-mm/20220810160209.1630707-1-Liam.Howlett@oracle.com/
> 
> I moved "binder_alloc: add missing mmap_lock calls when using the VMA"
> into mm-hotfixes-stable this week.
> 
> It's the v2.  I intend to send this Linuswards today or tomorrow.  Below.
> 
> So I think we're all good.
> 
> 
> commit b3bb668f3dc6a97a91c47a4cebb0e3f33554c08c

...

Sounds good, as long as it isn't the above commit which is v1, but
d6f35446d076 which is v2 :)

Thanks,
Liam