From: "Dmitry V. Levin" <ldv@altlinux.org>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: Szunti <szunti@gmail.com>,
Alejandro Colomar <alx.manpages@gmail.com>,
linux-man <linux-man@vger.kernel.org>
Subject: Re: user_namespaces(7) should mention overlay as mountable since Linux 5.11
Date: Mon, 15 Mar 2021 02:20:09 +0300 [thread overview]
Message-ID: <20210314232009.GA2561@altlinux.org> (raw)
In-Reply-To: <CAKgNAkh9XgUT+257TLtKBHsxuOHopqt76BL2xCz+JN2=u-xm=w@mail.gmail.com>
Hi Michael,
On Sun, Mar 14, 2021 at 11:04:26PM +0100, Michael Kerrisk (man-pages) wrote:
> On Tue, 9 Mar 2021 at 16:00, Szunti <szunti@gmail.com> wrote:
> >
> > 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)
It should rather say overlayfs.
> Could you add some info about how you discovered/verified this please.
>
> That helps us check the details.
What a coincidence, I just happen to have the relevant Linux kernel
merge commits cached:
92dbc9dedccb9759c7f9f2f0ae6242396376988f aka v5.11-rc1~83
4cb2c00c43b3fe88b32f29df4f76da1b92c33224 aka v5.11-rc7~28
--
ldv
next prev parent reply other threads:[~2021-03-14 23:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 15:00 user_namespaces(7) should mention overlay as mountable since Linux 5.11 Szunti
2021-03-14 22:04 ` Michael Kerrisk (man-pages)
2021-03-14 23:20 ` Dmitry V. Levin [this message]
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=20210314232009.GA2561@altlinux.org \
--to=ldv@altlinux.org \
--cc=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=szunti@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