From: David Howells <dhowells@redhat.com>
To: mtk.manpages@gmail.com
Cc: dhowells@redhat.com, Alexander Viro <viro@zeniv.linux.org.uk>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Christian Brauner <christian.brauner@ubuntu.com>,
linux-man <linux-man@vger.kernel.org>,
Linux API <linux-api@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>, Karel Zak <kzak@redhat.com>
Subject: Re: [PATCH 2/5] Add manpages for move_mount(2) and open_tree(2)
Date: Mon, 24 Aug 2020 11:08:22 +0100 [thread overview]
Message-ID: <287644.1598263702@warthog.procyon.org.uk> (raw)
In-Reply-To: <CAKgNAkjHcxYpzVohhJnxcHXO4s-4Ti_pNsmTZrD-CMu-EUCOoA@mail.gmail.com>
Michael Kerrisk (man-pages) <mtk.manpages@gmail.com> wrote:
> > +To access the source mount object or the destination mountpoint, no
> > +permissions are required on the object itself, but if either pathname is
> > +supplied, execute (search) permission is required on all of the directories
> > +specified in
> > +.IR from_pathname " or " to_pathname .
> > +.PP
> > +The caller does, however, require the appropriate capabilities or permission
> > +to effect a mount.
>
> Maybe better: s/effect/create/
The mount has already been created. We're moving/attaching it. Maybe:
The caller does, however, require the appropriate privilege (Linux:
the CAP_SYS_ADMIN capability) to move or attach mounts.
David
next prev parent reply other threads:[~2020-08-24 10:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 14:02 [PATCH 1/5] Add manpage for open_tree(2) David Howells
2020-08-07 14:02 ` [PATCH 2/5] Add manpages for move_mount(2) and open_tree(2) David Howells
2020-08-22 20:04 ` Michael Kerrisk (man-pages)
2020-08-24 10:08 ` David Howells [this message]
2020-08-26 7:31 ` Michael Kerrisk (man-pages)
2020-08-07 14:02 ` [PATCH 3/5] Add manpage for fspick(2) David Howells
2020-08-22 20:05 ` Michael Kerrisk (man-pages)
2020-08-07 14:02 ` [PATCH 4/5] Add manpage for fsopen(2) and fsmount(2) David Howells
2020-08-22 20:08 ` Michael Kerrisk (man-pages)
2020-08-07 14:02 ` [PATCH 5/5] Add manpage for fsconfig(2) David Howells
2020-08-07 15:58 ` AW: " Walter Harms
2020-08-07 16:27 ` David Howells
2020-08-07 16:35 ` AW: " Walter Harms
2020-08-22 20:18 ` Michael Kerrisk (man-pages)
2020-08-22 20:01 ` [PATCH 1/5] Add manpage for open_tree(2) Michael Kerrisk (man-pages)
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=287644.1598263702@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=christian.brauner@ubuntu.com \
--cc=kzak@redhat.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@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).