From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Mike Rapoport <rppt@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.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: Thu, 18 Jun 2026 11:37:10 +0200 [thread overview]
Message-ID: <11bae87d-73e6-4946-a41f-c5542fb40b75@kernel.org> (raw)
In-Reply-To: <ajO7yI541hphWRb8@kernel.org>
On 6/18/26 11:35, Mike Rapoport wrote:
> On Thu, Jun 18, 2026 at 11:25:31AM +0200, David Hildenbrand (Arm) wrote:
>> On 6/18/26 11:21, Mike Rapoport wrote:
>>>
>>> Cleaner in what sense?
>>> Will be uglier for sure, just take a look at vma_can_userfault().
>>
>> I was thinking of this:
>>
>> diff --git a/mm/userfaultfd.c b/mm/userfaultfd.c
>> index 180bad42fc79..8a6803618a91 100644
>> --- a/mm/userfaultfd.c
>> +++ b/mm/userfaultfd.c
>> @@ -2029,7 +2029,10 @@ bool vma_can_userfault(struct vm_area_struct *vma,
>> vm_flags_t vm_flags,
>> {
>> const struct vm_uffd_ops *ops = vma_uffd_ops(vma);
>>
>> - if (vma->vm_flags & VM_DROPPABLE)
>> + if (vma->vm_flags & (VM_DROPPABLE | VM_SHADOW_STACK))
>> + return false;
>> +
>> + if (!is_vm_hugetlb_page(vma) && (vma->vm_flags & VM_SPECIAL))
>> return false;
>
> 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).
--
Cheers,
David
prev parent reply other threads:[~2026-06-18 9:37 UTC|newest]
Thread overview: 9+ 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) [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=11bae87d-73e6-4946-a41f-c5542fb40b75@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=brauner@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox