linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Paul Moore <paul@paul-moore.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	 Roberto Sassu <roberto.sassu@huaweicloud.com>,
	Liam.Howlett@oracle.com,  lorenzo.stoakes@oracle.com,
	vbabka@suse.cz, jannh@google.com,  linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, ebpqwerty472123@gmail.com,
	 zohar@linux.ibm.com, dmitry.kasatkin@gmail.com,
	eric.snowberg@oracle.com,  jmorris@namei.org, serge@hallyn.com,
	linux-integrity@vger.kernel.org,
	 linux-security-module@vger.kernel.org, bpf@vger.kernel.org,
	 linux-fsdevel@vger.kernel.org, stable@vger.kernel.org,
	 syzbot+1cd571a672400ef3a930@syzkaller.appspotmail.com,
	 Roberto Sassu <roberto.sassu@huawei.com>
Subject: Re: [PATCH v2] mm: Split critical region in remap_file_pages() and invoke LSMs in between
Date: Tue, 22 Oct 2024 12:27:21 -0400	[thread overview]
Message-ID: <CAHC9VhRxXAj3ee0z7eMAiDYJ858xOgRyBTwCjvTRfNzDqt6yVw@mail.gmail.com> (raw)
In-Reply-To: <20241021200636.308f155a72f8a4d1e26f82b8@linux-foundation.org>

On Mon, Oct 21, 2024 at 11:06 PM Andrew Morton
<akpm@linux-foundation.org> wrote:
> On Sat, 19 Oct 2024 11:34:08 -0400 Paul Moore <paul@paul-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@paul-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 ...

That sounds good to me, I just wanted to make sure there was a path
forward to get into Linus' tree.

> ... but I
> can include it in this week's batch if we know that -next testing is
> hurting from it?

I don't believe so, I think this was just a syzbot gotcha.  From what
I understand remap_file_pages(2) isn't used much anymore.

-- 
paul-moore.com


      reply	other threads:[~2024-10-22 16:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-18 16:14 Roberto Sassu
2024-10-18 16:48 ` Liam R. Howlett
2024-10-18 19:04 ` Jarkko Sakkinen
2024-10-19 15:34 ` Paul Moore
2024-10-21  7:59   ` Roberto Sassu
2024-10-22  3:06   ` Andrew Morton
2024-10-22 16:27     ` Paul Moore [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAHC9VhRxXAj3ee0z7eMAiDYJ858xOgRyBTwCjvTRfNzDqt6yVw@mail.gmail.com \
    --to=paul@paul-moore.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=bpf@vger.kernel.org \
    --cc=dmitry.kasatkin@gmail.com \
    --cc=ebpqwerty472123@gmail.com \
    --cc=eric.snowberg@oracle.com \
    --cc=jannh@google.com \
    --cc=jmorris@namei.org \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=roberto.sassu@huawei.com \
    --cc=roberto.sassu@huaweicloud.com \
    --cc=serge@hallyn.com \
    --cc=stable@vger.kernel.org \
    --cc=syzbot+1cd571a672400ef3a930@syzkaller.appspotmail.com \
    --cc=vbabka@suse.cz \
    --cc=zohar@linux.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox