From: Peter Xu <peterx@redhat.com>
To: Tal Zussman <tz2294@columbia.edu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"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>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 3/3] userfaultfd: remove UFFD_CLOEXEC, UFFD_NONBLOCK, and UFFD_FLAGS_SET
Date: Wed, 4 Jun 2025 11:17:17 -0400 [thread overview]
Message-ID: <aEBjfQfD4rujNlaf@x1.local> (raw)
In-Reply-To: <20250603-uffd-fixes-v1-3-9c638c73f047@columbia.edu>
On Tue, Jun 03, 2025 at 06:14:22PM -0400, Tal Zussman wrote:
> UFFD_CLOEXEC, UFFD_NONBLOCK, and UFFD_FLAGS_SET have been unused since they
> were added in commit 932b18e0aec6 ("userfaultfd: linux/userfaultfd_k.h").
> Remove them and the associated BUILD_BUG_ON() checks.
>
> Signed-off-by: Tal Zussman <tz2294@columbia.edu>
Acked-by: Peter Xu <peterx@redhat.com>
--
Peter Xu
prev parent reply other threads:[~2025-06-04 15:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 22:14 [PATCH 0/3] mm: userfaultfd: assorted fixes and cleanups Tal Zussman
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 [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=aEBjfQfD4rujNlaf@x1.local \
--to=peterx@redhat.com \
--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=tz2294@columbia.edu \
--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 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.