[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <287644.1598263702@warthog.procyon.org.uk>
Date: Mon, 24 Aug 2020 11:08:22 +0100
From: David Howells <dhowells@...hat.com>
To: mtk.manpages@...il.com
Cc: dhowells@...hat.com, Alexander Viro <viro@...iv.linux.org.uk>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
Christian Brauner <christian.brauner@...ntu.com>,
linux-man <linux-man@...r.kernel.org>,
Linux API <linux-api@...r.kernel.org>,
lkml <linux-kernel@...r.kernel.org>, Karel Zak <kzak@...hat.com>
Subject: Re: [PATCH 2/5] Add manpages for move_mount(2) and open_tree(2)
Michael Kerrisk (man-pages) <mtk.manpages@...il.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
Powered by blists - more mailing lists