From: Tal Zussman <tz2294@columbia.edu>
To: Andrew Morton <akpm@linux-foundation.org>,
Peter Xu <peterx@redhat.com>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
David Hildenbrand <david@redhat.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Pavel Emelyanov <xemul@parallels.com>,
Andrea Arcangeli <aarcange@redhat.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, Tal Zussman <tz2294@columbia.edu>
Subject: [PATCH 0/3] mm: userfaultfd: assorted fixes and cleanups
Date: Tue, 03 Jun 2025 18:14:19 -0400 [thread overview]
Message-ID: <20250603-uffd-fixes-v1-0-9c638c73f047@columbia.edu> (raw)
Two fixes and one cleanup for userfaultfd.
The second patch is a more of an RFC, as it changes previously allowed
user behavior. However, being able to unregister memory through a uffd
different from the uffd it was originally registered with seems odd enough
that I'd argue it's a bug :)
---
Tal Zussman (3):
userfaultfd: correctly prevent registering VM_DROPPABLE regions
userfaultfd: prevent unregistering VMAs through a different userfaultfd
userfaultfd: remove UFFD_CLOEXEC, UFFD_NONBLOCK, and UFFD_FLAGS_SET
fs/userfaultfd.c | 17 +++++++++++++----
include/linux/userfaultfd_k.h | 6 +-----
2 files changed, 14 insertions(+), 9 deletions(-)
---
base-commit: 546b1c9e93c2bb8cf5ed24e0be1c86bb089b3253
change-id: 20250531-uffd-fixes-142331b15e63
Best regards,
--
Tal Zussman <tz2294@columbia.edu>
next reply other threads:[~2025-06-03 22:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 22:14 Tal Zussman [this message]
2025-06-03 22:14 ` [PATCH 1/3] userfaultfd: correctly prevent registering VM_DROPPABLE regions Tal Zussman
2025-06-04 13:19 ` David Hildenbrand
2025-06-04 15:17 ` Peter Xu
2025-06-03 22:14 ` [PATCH 2/3] userfaultfd: prevent unregistering VMAs through a different userfaultfd Tal Zussman
2025-06-04 0:52 ` James Houghton
2025-06-05 20:56 ` Tal Zussman
2025-06-04 13:23 ` David Hildenbrand
2025-06-04 15:09 ` Peter Xu
2025-06-05 21:06 ` David Hildenbrand
2025-06-05 21:15 ` Tal Zussman
2025-06-06 13:03 ` Peter Xu
2025-06-06 13:15 ` David Hildenbrand
2025-06-05 21:11 ` Tal Zussman
2025-06-06 13:24 ` Peter Xu
2025-06-06 19:15 ` Tal Zussman
2025-06-05 21:06 ` Tal Zussman
2025-06-03 22:14 ` [PATCH 3/3] userfaultfd: remove UFFD_CLOEXEC, UFFD_NONBLOCK, and UFFD_FLAGS_SET Tal Zussman
2025-06-04 13:24 ` David Hildenbrand
2025-06-04 15:17 ` Peter Xu
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=20250603-uffd-fixes-v1-0-9c638c73f047@columbia.edu \
--to=tz2294@columbia.edu \
--cc=Jason@zx2c4.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=david@redhat.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterx@redhat.com \
--cc=viro@zeniv.linux.org.uk \
--cc=xemul@parallels.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