From: Christian Brauner <brauner@kernel.org>
To: linux-man@vger.kernel.org,
Alejandro Colomar <alx.manpages@gmail.com>,
Michael Kerrisk <mtk.manpages@gmail.com>
Cc: Christian Brauner <brauner@kernel.org>,
Christoph Hellwig <hch@infradead.org>,
Aleksa Sarai <cyphar@cyphar.com>
Subject: [PATCH 2/4] mount_setattr.2: update conditions to create ID-mapped mounts
Date: Tue, 7 Jun 2022 15:38:18 +0200 [thread overview]
Message-ID: <20220607133820.1721352-3-brauner@kernel.org> (raw)
In-Reply-To: <20220607133820.1721352-1-brauner@kernel.org>
Newer kernels in principle support the creation of ID-mapped mounts for
filesystems mountable in non-initial user namespaces. Currently, no such
filesystem has been ported to support this though. But we should
nonetheless update the conditions.
Signed-off-by: Christian Brauner (Microsoft) <brauner@kernel.org>
---
man2/mount_setattr.2 | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/man2/mount_setattr.2 b/man2/mount_setattr.2
index 2bf1b24da..0999373d6 100644
--- a/man2/mount_setattr.2
+++ b/man2/mount_setattr.2
@@ -649,10 +649,11 @@ The following conditions must be met in order to create an ID-mapped mount:
.IP \(bu 3
The caller must have the
.B CAP_SYS_ADMIN
-capability in the initial user namespace.
-.IP \(bu
-The filesystem must be mounted in a mount namespace
-that is owned by the initial user namespace.
+capability in the user namespace the filesystem was mounted in.
+.\" commit bd303368b776eead1c29e6cdda82bde7128b82a7
+.\" Christian Brauner
+.\" Note, currently no filesystems mountable in non-initial user namespaces
+.\" support ID-mapped mounts.
.IP \(bu
The underlying filesystem must support ID-mapped mounts.
Currently, the
--
2.34.1
next prev parent reply other threads:[~2022-06-07 13:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 13:38 [PATCH 0/4] mount_setattr.2: updates Christian Brauner
2022-06-07 13:38 ` [PATCH 1/4] mount_setattr.2: add and explain missing EBUSY error Christian Brauner
2022-06-07 13:38 ` Christian Brauner [this message]
2022-06-07 13:38 ` [PATCH 3/4] mount_setattr.2: update list of supported filesystems Christian Brauner
2022-06-07 13:38 ` [PATCH 4/4] mount_setattr.2: ffix Christian Brauner
2022-06-08 15:26 ` [PATCH 0/4] mount_setattr.2: updates Alejandro Colomar
2022-06-08 15:28 ` 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=20220607133820.1721352-3-brauner@kernel.org \
--to=brauner@kernel.org \
--cc=alx.manpages@gmail.com \
--cc=cyphar@cyphar.com \
--cc=hch@infradead.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