From: Aleksa Sarai <cyphar@cyphar.com>
To: Al Viro <viro@zeniv.linux.org.uk>,
Michael Kerrisk <mtk.manpages@gmail.com>
Cc: Aleksa Sarai <cyphar@cyphar.com>,
Christian Brauner <christian@brauner.io>,
Aleksa Sarai <asarai@suse.de>,
linux-man@vger.kernel.org, linux-api@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH RFC 0/3] document openat2(2) patch series
Date: Fri, 4 Oct 2019 00:55:38 +1000 [thread overview]
Message-ID: <20191003145542.17490-1-cyphar@cyphar.com> (raw)
This is a first draft of the man-page changes for the openat2(2) patch
series I'm working on[1]. It includes information about the magic-link
changes as well as the primary new features (O_EMPTYPATH and openat2).
Let me know what you think. I might go into too much detail about how
extension of openat2(2) will work -- let me know if that section should
be dropped (while it is useful for userspace to understand, it isn't
really that necessary to explain exactly what the semantics are -- it
will usually just transparently work).
[1]: https://lore.kernel.org/lkml/20190930183316.10190-1-cyphar@cyphar.com/
Aleksa Sarai (3):
symlink.7: document magic-links more completely
open.2: add O_EMPTYPATH documentation
openat2.2: document new openat2(2) syscall
man2/open.2 | 47 ++++-
man2/openat2.2 | 381 +++++++++++++++++++++++++++++++++++++++++
man7/path_resolution.7 | 89 ++++++++--
man7/symlink.7 | 39 ++++-
4 files changed, 528 insertions(+), 28 deletions(-)
create mode 100644 man2/openat2.2
--
2.23.0
next reply other threads:[~2019-10-03 14:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 14:55 Aleksa Sarai [this message]
2019-10-03 14:55 ` [PATCH RFC 1/3] symlink.7: document magic-links more completely Aleksa Sarai
2019-10-07 16:36 ` Jann Horn
2019-10-08 1:33 ` Aleksa Sarai
2019-10-09 7:55 ` Michael Kerrisk (man-pages)
2019-10-09 9:57 ` Aleksa Sarai
2020-04-17 11:39 ` Michael Kerrisk (man-pages)
2020-04-17 15:37 ` Aleksa Sarai
2020-05-15 11:42 ` Michael Kerrisk (man-pages)
2019-10-03 14:55 ` [PATCH RFC 2/3] open.2: add O_EMPTYPATH documentation Aleksa Sarai
2019-10-09 8:01 ` Michael Kerrisk (man-pages)
2019-10-09 10:00 ` Aleksa Sarai
2019-10-03 14:55 ` [PATCH RFC 3/3] openat2.2: document new openat2(2) syscall Aleksa Sarai
2019-10-09 8:36 ` Michael Kerrisk (man-pages)
2019-10-09 10:17 ` Aleksa Sarai
2019-10-09 10:32 ` Michael Kerrisk (man-pages)
2019-10-03 14:55 ` [PATCH RFC 3/3] openat2.2: document new syscall Aleksa Sarai
2019-10-03 15:00 ` Aleksa Sarai
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=20191003145542.17490-1-cyphar@cyphar.com \
--to=cyphar@cyphar.com \
--cc=asarai@suse.de \
--cc=christian@brauner.io \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).