[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250603-uffd-fixes-v1-0-9c638c73f047@columbia.edu>
Date: Tue, 03 Jun 2025 18:14:19 -0400
From: Tal Zussman <tz2294@...umbia.edu>
To: Andrew Morton <akpm@...ux-foundation.org>, Peter Xu <peterx@...hat.com>,
"Jason A. Donenfeld" <Jason@...c4.com>,
David Hildenbrand <david@...hat.com>,
Alexander Viro <viro@...iv.linux.org.uk>,
Christian Brauner <brauner@...nel.org>, Jan Kara <jack@...e.cz>,
Pavel Emelyanov <xemul@...allels.com>,
Andrea Arcangeli <aarcange@...hat.com>
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, Tal Zussman <tz2294@...umbia.edu>
Subject: [PATCH 0/3] mm: userfaultfd: assorted fixes and cleanups
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@...umbia.edu>
Powered by blists - more mailing lists