From: Peter Xu <peterx@redhat.com>
To: Ian Abbott <abbotti@mev.co.uk>
Cc: linux-man@vger.kernel.org,
Alejandro Colomar <alx.manpages@gmail.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
linux-kernel@vger.kernel.org,
Axel Rasmussen <axelrasmussen@google.com>
Subject: Re: [PATCH] ioctl_userfaultfd.2: Corrections for returned .ioctls members
Date: Mon, 21 Mar 2022 14:10:52 +0800 [thread overview]
Message-ID: <YjgW7L77+Y2fylcR@xz-m1.local> (raw)
In-Reply-To: <20220318191343.72812-1-abbotti@mev.co.uk>
On Fri, Mar 18, 2022 at 07:13:43PM +0000, Ian Abbott wrote:
> Support for the `UFFDIO_WRITEPROTECT` operation is not indicated in the
> `ioctls` member of `struct uffdio_api`. It is indicated in the `ioctls`
> member of `struct uffdio_register` along with indications of support for
> the `UFFDIO_COPY`, `UFFDIO_WAKE` and `UFFDIO_ZEROPAGE` operations (and
> also the `UFFDIO_CONTINUE` operation supported since Linux 5.13 but
> that is not documented by this man page yet.)
I thought it should have landed but indeed it's not. Copying Axel.
>
> Fixes: f559fa36a678 ("ioctl_userfaultfd.2: Add write-protect mode docs")
> Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
The patch looks correct to me, thanks for fixing it.
Acked-by: Peter Xu <peterx@redhat.com>
> ---
> man2/ioctl_userfaultfd.2 | 27 ++++++++++++++++++++-------
> 1 file changed, 20 insertions(+), 7 deletions(-)
>
> diff --git a/man2/ioctl_userfaultfd.2 b/man2/ioctl_userfaultfd.2
> index 504f61d4b..e930af520 100644
> --- a/man2/ioctl_userfaultfd.2
> +++ b/man2/ioctl_userfaultfd.2
> @@ -235,11 +235,6 @@ operation is supported.
> The
> .B UFFDIO_UNREGISTER
> operation is supported.
> -.TP
> -.B 1 << _UFFDIO_WRITEPROTECT
> -The
> -.B UFFDIO_WRITEPROTECT
> -operation is supported.
> .PP
> This
> .BR ioctl (2)
> @@ -333,8 +328,26 @@ If the operation is successful, the kernel modifies the
> bit-mask field to indicate which
> .BR ioctl (2)
> operations are available for the specified range.
> -This returned bit mask is as for
> -.BR UFFDIO_API .
> +This returned bit mask can contain the following bits:
> +.TP
> +.B 1 << _UFFDIO_COPY
> +The
> +.B UFFDIO_COPY
> +operation is supported.
> +.TP
> +.B 1 << _UFFDIO_WAKE
> +The
> +.B UFFDIO_WAKE
> +operation is supported.
> +.TP
> +.B 1 << _UFFDIO_WRITEPROTECT
> +The
> +.B UFFDIO_WRITEPROTECT
> +.TP
> +.B 1 << _UFFDIO_ZEROPAGE
> +The
> +.B UFFDIO_ZEROPAGE
> +operation is supported.
> .PP
> This
> .BR ioctl (2)
> --
--
Peter Xu
next prev parent reply other threads:[~2022-03-21 6:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 19:13 [PATCH] ioctl_userfaultfd.2: Corrections for returned .ioctls members Ian Abbott
2022-03-21 6:10 ` Peter Xu [this message]
2022-03-22 12:32 ` Alejandro Colomar (man-pages)
2022-03-22 16:23 ` Axel Rasmussen
2022-03-22 16:36 ` Axel Rasmussen
2022-03-22 16:46 ` Ian Abbott
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=YjgW7L77+Y2fylcR@xz-m1.local \
--to=peterx@redhat.com \
--cc=abbotti@mev.co.uk \
--cc=alx.manpages@gmail.com \
--cc=axelrasmussen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@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