linux-kernel - Re: [PATCH v2] mm: Split critical region in remap_file

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: <20241021200636.308f155a72f8a4d1e26f82b8@linux-foundation.org>
Date: Mon, 21 Oct 2024 20:06:36 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Paul Moore <paul@...l-moore.com>
Cc: "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>, Roberto Sassu
 <roberto.sassu@...weicloud.com>, Liam.Howlett@...cle.com,
 lorenzo.stoakes@...cle.com, vbabka@...e.cz, jannh@...gle.com,
 linux-mm@...ck.org, linux-kernel@...r.kernel.org,
 ebpqwerty472123@...il.com, zohar@...ux.ibm.com, dmitry.kasatkin@...il.com,
 eric.snowberg@...cle.com, jmorris@...ei.org, serge@...lyn.com,
 linux-integrity@...r.kernel.org, linux-security-module@...r.kernel.org,
 bpf@...r.kernel.org, linux-fsdevel@...r.kernel.org, stable@...r.kernel.org,
 syzbot+1cd571a672400ef3a930@...kaller.appspotmail.com, Roberto Sassu
 <roberto.sassu@...wei.com>
Subject: Re: [PATCH v2] mm: Split critical region in remap_file_pages() and
 invoke LSMs in between

On Sat, 19 Oct 2024 11:34:08 -0400 Paul Moore <paul@...l-moore.com> wrote:

> >  mm/mmap.c | 69 +++++++++++++++++++++++++++++++++++++++++--------------
> >  1 file changed, 52 insertions(+), 17 deletions(-)
> 
> Thanks for working on this Roberto, Kirill, and everyone else who had
> a hand in reviewing and testing.
> 
> Reviewed-by: Paul Moore <paul@...l-moore.com>
> 
> Andrew, I see you're pulling this into the MM/hotfixes-unstable
> branch, do you also plan to send this up to Linus soon/next-week?  If
> so, great, if not let me know and I can send it up via the LSM tree.

In the normal course of things I'd send it upstream next week, but I
can include it in this week's batch if we know that -next testing is
hurting from it?