From: Axel Rasmussen <axelrasmussen@google.com>
To: Alejandro Colomar <alx@kernel.org>, Peter Xu <peterx@redhat.com>
Cc: linux-man@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Axel Rasmussen <axelrasmussen@google.com>
Subject: [PATCH v2 0/5] userfaultfd man page updates
Date: Tue, 3 Oct 2023 12:45:42 -0700 [thread overview]
Message-ID: <20231003194547.2237424-1-axelrasmussen@google.com> (raw)
This series includes only the remaining patches not applied from v1, with
review comments addressed. This series is based on the "contrib" branch.
Changelog:
v1->v2:
- In patch 1 (patch 5 in v1), change "after" to "since" for consistency and to
be clear that we mean 4.11+ (inclusive).
- In patch 2 (patch 7 in v1), reorder error codes alphabetically (EINVAL then
EPERM).
- In patch 3 (patch 8 in v1), resolve conflicts with earlier review comments.
Original cover letter:
Various updates for userfaultfd man pages. To summarize the changes:
- Correctly / fully describe the two-step feature support handshake process.
- Describe new UFFDIO_POISON ioctl.
- Other small improvements (missing ioctls, error codes, etc).
Axel Rasmussen (5):
ioctl_userfaultfd.2: describe two-step feature handshake
ioctl_userfaultfd.2: correct and update UFFDIO_API ioctl error codes
ioctl_userfaultfd.2: clarify the state of the uffdio_api structure on
error
ioctl_userfaultfd.2: fix / update UFFDIO_REGISTER error code list
ioctl_userfaultfd.2: document new UFFDIO_POISON ioctl
man2/ioctl_userfaultfd.2 | 226 +++++++++++++++++++++++++++++++--------
1 file changed, 181 insertions(+), 45 deletions(-)
--
2.42.0.609.gbb76f46606-goog
next reply other threads:[~2023-10-03 19:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 19:45 Axel Rasmussen [this message]
2023-10-03 19:45 ` [PATCH v2 1/5] ioctl_userfaultfd.2: describe two-step feature handshake Axel Rasmussen
2023-10-08 22:23 ` Alejandro Colomar
2023-10-03 19:45 ` [PATCH v2 2/5] ioctl_userfaultfd.2: correct and update UFFDIO_API ioctl error codes Axel Rasmussen
2023-10-08 22:25 ` Alejandro Colomar
2023-10-03 19:45 ` [PATCH v2 3/5] ioctl_userfaultfd.2: clarify the state of the uffdio_api structure on error Axel Rasmussen
2023-10-08 21:52 ` Alejandro Colomar
2023-10-09 9:12 ` Mike Rapoport
2023-10-03 19:45 ` [PATCH v2 4/5] ioctl_userfaultfd.2: fix / update UFFDIO_REGISTER error code list Axel Rasmussen
2023-10-08 22:06 ` Alejandro Colomar
2023-10-17 21:23 ` Guillem Jover
2023-10-17 21:42 ` Alejandro Colomar
2023-10-17 22:14 ` Axel Rasmussen
2023-10-03 19:45 ` [PATCH v2 5/5] ioctl_userfaultfd.2: document new UFFDIO_POISON ioctl Axel Rasmussen
2023-10-08 22:23 ` Alejandro Colomar
2023-10-17 22:25 ` Axel Rasmussen
2023-10-08 22:27 ` [PATCH v2 0/5] userfaultfd man page updates 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=20231003194547.2237424-1-axelrasmussen@google.com \
--to=axelrasmussen@google.com \
--cc=alx@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterx@redhat.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