All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lorenzo Stoakes <ljs@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Mike Rapoport <rppt@kernel.org>,
	 "David Hildenbrand (Arm)" <david@kernel.org>,
	Linus Torvalds <torvalds@linuxfoundation.org>,
	 Alexander Viro <viro@zeniv.linux.org.uk>,
	Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
	 Oleg Nesterov <oleg@redhat.com>, Peter Xu <peterx@redhat.com>,
	 vova tokarev <vladimirelitokarev@gmail.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	 stable@vger.kernel.org
Subject: Re: [PATCH] userfaultfd: prevent registration of special VMAs
Date: Tue, 7 Jul 2026 08:23:57 +0100	[thread overview]
Message-ID: <akypf9pq8NCeZlMi@lucifer> (raw)
In-Reply-To: <20260705005124.307e2379ab03109e5f77bd1c@linux-foundation.org>

On Sun, Jul 05, 2026 at 12:51:24AM -0700, Andrew Morton wrote:
> On Fri, 3 Jul 2026 14:38:56 +0100 Lorenzo Stoakes <ljs@kernel.org> wrote:
>
> > On Fri, Jul 03, 2026 at 04:20:37PM +0300, Mike Rapoport wrote:
> > > On Fri, Jul 03, 2026 at 11:11:14AM +0100, Lorenzo Stoakes wrote:
> > > > On Thu, Jun 18, 2026 at 11:37:10AM +0200, David Hildenbrand (Arm) wrote:
> > > > > > In a way that's an extra check for hugetlb, but it will work.
> > > > >
> > > > > My point would be that we exclude all special VMAs, except hugetlb (which is
> > > > > special but supported ... in its special way).
> > > >
> > > > Mike - you said you were respinning, it'd help my series if you respan the above
> > > > quickly so I could base my change on that :).
> > >
> > > I sent it already:
> > >
> > > https://lore.kernel.org/all/20260618095017.2553004-1-rppt@kernel.org
> > >
> > > and Andrew apparently ook it:
> > >
> > > https://lore.kernel.org/all/20260618183442.BBCD71F000E9@smtp.kernel.org
> >
> > It's not anywhere :)
> >
> > Andrew - did you take that thread as signal this should not go in?
> >
> > It should definitely go in. I will clean up the mess discussed there separately.
>
> Thanks, yes, I added it then hid it when Linus objected.  I'll unhide
> it now.

Thanks!


      reply	other threads:[~2026-07-07  7:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-17 19:40 [PATCH] userfaultfd: prevent registration of special VMAs Mike Rapoport
2026-06-18  8:19 ` David Hildenbrand (Arm)
2026-06-18  8:34   ` Mike Rapoport
2026-06-18  8:43     ` Mike Rapoport
2026-06-18  8:47       ` David Hildenbrand (Arm)
2026-06-18  9:21         ` Mike Rapoport
2026-06-18  9:25           ` David Hildenbrand (Arm)
2026-06-18  9:35             ` Mike Rapoport
2026-06-18  9:37               ` David Hildenbrand (Arm)
2026-07-03 10:11                 ` Lorenzo Stoakes
2026-07-03 13:20                   ` Mike Rapoport
2026-07-03 13:38                     ` Lorenzo Stoakes
2026-07-05  7:51                       ` Andrew Morton
2026-07-07  7:23                         ` Lorenzo Stoakes [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=akypf9pq8NCeZlMi@lucifer \
    --to=ljs@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=brauner@kernel.org \
    --cc=david@kernel.org \
    --cc=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=oleg@redhat.com \
    --cc=peterx@redhat.com \
    --cc=rppt@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linuxfoundation.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=vladimirelitokarev@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.