From: Christian Brauner <christian.brauner@ubuntu.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: Alejandro Colomar <alx.manpages@gmail.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
linux-man <linux-man@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: Questions re the new mount_setattr(2) manual page
Date: Tue, 10 Aug 2021 16:11:25 +0200 [thread overview]
Message-ID: <20210810141125.nxmvnwpyjxajvxl4@wittgenstein> (raw)
In-Reply-To: <b23122c0-893a-c1b4-0b2d-3a332af4151f@gmail.com>
On Tue, Aug 10, 2021 at 09:12:14AM +0200, Michael Kerrisk (man-pages) wrote:
> Hi Christian,
>
> One more question...
>
> >> The propagation field is used to specify the propagation typ
> >> of the mount or mount tree. Mount propagation options are
> >> mutually exclusive; that is, the propagation values behave
> >> like an enum. The supported mount propagation types are:
>
> The manual page text doesn't actually say it, but if the 'propagation'
> field is 0, then this means leave the propagation type unchanged,
> right? This of course should be mentioned in the manual page.
Yes, if none of the documented values is set the propagation is unchanged.
Christian
next prev parent reply other threads:[~2021-08-10 14:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 1:38 Questions re the new mount_setattr(2) manual page Michael Kerrisk (man-pages)
2021-08-10 7:12 ` Michael Kerrisk (man-pages)
2021-08-10 14:11 ` Christian Brauner [this message]
2021-08-10 19:30 ` Michael Kerrisk (man-pages)
2021-08-10 14:32 ` Christian Brauner
2021-08-10 21:06 ` Michael Kerrisk (man-pages)
2021-08-11 10:07 ` Christian Brauner
2021-08-12 5:36 ` Michael Kerrisk (man-pages)
2021-08-12 9:08 ` Christian Brauner
2021-08-12 22:32 ` Michael Kerrisk (man-pages)
2021-08-10 22:47 ` Michael Kerrisk (man-pages)
2021-08-11 10:40 ` Christian Brauner
2021-08-12 5:36 ` Michael Kerrisk (man-pages)
2021-08-12 8:38 ` Christian Brauner
2021-08-13 1:25 ` 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=20210810141125.nxmvnwpyjxajvxl4@wittgenstein \
--to=christian.brauner@ubuntu.com \
--cc=alx.manpages@gmail.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).