From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: mtk.manpages@gmail.com, lkml <linux-kernel@vger.kernel.org>,
"linux-man@vger.kernel.org" <linux-man@vger.kernel.org>,
containers@lists.linux-foundation.org,
Andy Lutomirski <luto@amacapital.net>,
richard.weinberger@gmail.com,
"Serge E. Hallyn" <serge@hallyn.com>
Subject: Re: For review: user_namespace(7) man page
Date: Thu, 11 Sep 2014 07:40:12 -0700 [thread overview]
Message-ID: <5411B44C.5050405@gmail.com> (raw)
In-Reply-To: <87bnqon513.fsf@x220.int.ebiederm.org>
On 09/09/2014 09:16 AM, Eric W. Biederman wrote:
>>> On a related note. One thing that has come up recently (in 3 separate
>>> >> implementations is that mount(MS_REMOUNT|...,...) must include all of
>>> >> the mount flags that need to be preserved. People creating read-only
>>> >> bind mounts tend to miss that and the locked flags in mount namespaces.
>>> >> That issue was flushed out now that the kernel is now not allowing most
>>> >> mount flags to be cleared in mount namespaces.
>> >
>> > So, are you meaning that something needs to be added to the page
>> > regarding this point?
> Yes. The interface is non-intuitive and we should at least document
> the weirdness.
Okay -- I have added that piece to mount(2).
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2014-09-11 14:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 23:36 Michael Kerrisk (man-pages)
2014-08-22 21:12 ` Serge E. Hallyn
2014-09-01 16:58 ` Michael Kerrisk (man-pages)
2014-08-30 21:53 ` Eric W. Biederman
2014-09-01 17:31 ` Michael Kerrisk (man-pages)
2014-09-02 1:05 ` Eric W. Biederman
2014-09-09 14:00 ` Michael Kerrisk (man-pages)
2014-09-09 16:16 ` Eric W. Biederman
2014-09-11 14:40 ` Michael Kerrisk (man-pages) [this message]
2014-09-09 13:59 ` Michael Kerrisk (man-pages)
2014-09-09 15:49 ` Eric W. Biederman
2014-09-11 14:40 ` Michael Kerrisk (man-pages)
2014-09-09 13:59 ` Michael Kerrisk (man-pages)
2014-09-09 15:51 ` Eric W. Biederman
2014-09-11 14:40 ` Michael Kerrisk (man-pages)
2014-09-01 20:57 ` Andy Lutomirski
2014-09-09 14:00 ` Michael Kerrisk (man-pages)
2014-09-09 16:05 ` Eric W. Biederman
2014-09-09 19:26 ` Andy Lutomirski
2014-09-09 19:39 ` Andy Lutomirski
2014-09-11 14:47 ` Michael Kerrisk (man-pages)
2014-09-11 15:15 ` Andy Lutomirski
2014-09-14 2:58 ` Michael Kerrisk (man-pages)
2014-09-11 14:46 ` Michael Kerrisk (man-pages)
2014-09-11 15:14 ` Andy Lutomirski
2014-09-14 2:42 ` 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=5411B44C.5050405@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=containers@lists.linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=richard.weinberger@gmail.com \
--cc=serge@hallyn.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
Powered by JetHome