From: Szunti <szunti@gmail.com>
To: "Michael Kerrisk" <mtk.manpages@gmail.com>,
"Alejandro Colomar" <alx.manpages@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: user_namespaces(7) should mention overlay as mountable since Linux 5.11
Date: Tue, 09 Mar 2021 16:00:19 +0100 [thread overview]
Message-ID: <87v9a0wews.fsf@gmail.com> (raw)
user_namespaces lists in Capabilities section the filesystems that can
be mount:
Holding CAP_SYS_ADMIN within the user namespace that owns a process's
mount namespace allows that process to create bind mounts and mount the
following types of filesystems:
* /proc (since Linux 3.8)
* /sys (since Linux 3.8)
* devpts (since Linux 3.9)
* tmpfs(5) (since Linux 3.9)
* ramfs (since Linux 3.9)
* mqueue (since Linux 3.9)
* bpf (since Linux 4.4)
IUUC this list should add
* overlay (since Linux 5.11)
next reply other threads:[~2021-03-09 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 15:00 Szunti [this message]
2021-03-14 22:04 ` user_namespaces(7) should mention overlay as mountable since Linux 5.11 Michael Kerrisk (man-pages)
2021-03-14 23:20 ` Dmitry V. Levin
2021-03-21 15:45 ` 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=87v9a0wews.fsf@gmail.com \
--to=szunti@gmail.com \
--cc=alx.manpages@gmail.com \
--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