From: Alejandro Colomar <alx@kernel.org>
To: Peter Xu <peterx@redhat.com>
Cc: linux-man@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Andrea Arcangeli <aarcange@redhat.com>,
Kyle Huey <me@kylehuey.com>,
Robert O'Callahan <robert@ocallahan.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Axel Rasmussen <axelrasmussen@google.com>,
Kyle Huey <khuey@kylehuey.com>
Subject: Re: [PATCH v2 1/2] UFFDIO_API.2const: Update userfaultfd handshake and feature probe
Date: Sun, 18 May 2025 10:18:30 +0200 [thread overview]
Message-ID: <gwzis5sso3a5g4a7b5tplyfj473b35jzy2cmabs6lgtwa4bc4b@ez3rlmdxphea> (raw)
In-Reply-To: <20250514172630.569788-2-peterx@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 3098 bytes --]
Hi Peter,
On Wed, May 14, 2025 at 01:26:29PM -0400, Peter Xu wrote:
> There's a confusing paragraph in the man page on two-steps handshake for
> userfaultfd UFFDIO_API ioctl. In reality, after a successful UFFDIO_API
> ioctl, the userfaultfd will be locked up on the features and any further
> UFFDIO_API on top of an initialized userfaultfd would fail.
>
> Modify the UFFDIO_API(2const) man page to reflect the reality. Instead,
> add a paragraph explaining the right way to probe userfaultfd features.
> Add that only after the "Before Linux 4.11" paragraph, as the old kernel
> doesn't support any feature anyway.
>
> Fixes: a252b3345 ("ioctl_userfaultfd.2: Describe two-step feature handshake")
> Reviewed-by: Kyle Huey <khuey@kylehuey.com>
> Signed-off-by: Peter Xu <peterx@redhat.com>
Thanks! I've applied the patch.
Have a lovely day!
Alex
> ---
> man/man2const/UFFDIO_API.2const | 44 +++++++++++++++++++--------------
> 1 file changed, 25 insertions(+), 19 deletions(-)
>
> diff --git a/man/man2const/UFFDIO_API.2const b/man/man2const/UFFDIO_API.2const
> index 54b34a1bc..aca27dc5c 100644
> --- a/man/man2const/UFFDIO_API.2const
> +++ b/man/man2const/UFFDIO_API.2const
> @@ -42,25 +42,6 @@ fields to bit masks representing all the available features and the generic
> .BR ioctl (2)
> operations available.
> .P
> -Since Linux 4.11,
> -applications should use the
> -.I features
> -field to perform a two-step handshake.
> -First,
> -.B UFFDIO_API
> -is called with the
> -.I features
> -field set to zero.
> -The kernel responds by setting all supported feature bits.
> -.P
> -Applications which do not require any specific features
> -can begin using the userfaultfd immediately.
> -Applications which do need specific features
> -should call
> -.B UFFDIO_API
> -again with a subset of the reported feature bits set
> -to enable those features.
> -.P
> Before Linux 4.11, the
> .I features
> field must be initialized to zero before the call to
> @@ -70,6 +51,31 @@ and zero (i.e., no feature bits) is placed in the
> field by the kernel upon return from
> .BR ioctl (2).
> .P
> +Since Linux 4.11,
> +userfaultfd supports features that need to be enabled explicitly.
> +To enable any of the features,
> +one needs to set the corresponding feature bits in
> +.I features
> +when issuing the
> +.B UFFDIO_API
> +ioctl.
> +.P
> +For historical reasons,
> +a temporary userfaultfd is needed to probe
> +what userfaultfd features the kernel supports.
> +The application needs to create a temporary userfaultfd,
> +issue an
> +.B UFFDIO_API
> +ioctl with
> +.I features
> +set to zero.
> +After the
> +.B UFFDIO_API
> +ioctl returns successfully,
> +.I features
> +should contain all the userfaultfd features that the kernel supports.
> +The temporary userfaultfd can be safely closed after the probe.
> +.P
> If the application sets unsupported feature bits,
> the kernel will zero out the returned
> .I uffdio_api
> --
> 2.49.0
>
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-05-18 8:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 17:26 [PATCH v2 0/2] UFFDIO_API.2const: Two man page updates Peter Xu
2025-05-14 17:26 ` [PATCH v2 1/2] UFFDIO_API.2const: Update userfaultfd handshake and feature probe Peter Xu
2025-05-18 8:18 ` Alejandro Colomar [this message]
2025-05-14 17:26 ` [PATCH v2 2/2] UFFDIO_API.2const: Add an entry for UFFDIO_FEATURE_MOVE Peter Xu
2025-05-18 8:19 ` Alejandro Colomar
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=gwzis5sso3a5g4a7b5tplyfj473b35jzy2cmabs6lgtwa4bc4b@ez3rlmdxphea \
--to=alx@kernel.org \
--cc=aarcange@redhat.com \
--cc=axelrasmussen@google.com \
--cc=khuey@kylehuey.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=me@kylehuey.com \
--cc=peterx@redhat.com \
--cc=robert@ocallahan.org \
--cc=rppt@kernel.org \
--cc=surenb@google.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