From: ebiederm@xmission.com (Eric W. Biederman)
To: Gao feng <gaofeng@cn.fujitsu.com>
Cc: serge.hallyn@canonical.com, akpm@linux-foundation.org,
containers@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] userns: Allow the unprivileged users to mount mqueue fs
Date: Sun, 27 Jan 2013 23:14:48 -0800 [thread overview]
Message-ID: <877gmxye1j.fsf@xmission.com> (raw)
In-Reply-To: <51061F2F.6040104@cn.fujitsu.com> (Gao feng's message of "Mon, 28 Jan 2013 14:48:15 +0800")
Gao feng <gaofeng@cn.fujitsu.com> writes:
> On 2013/01/28 11:43, Eric W. Biederman wrote:
>> Gao feng <gaofeng@cn.fujitsu.com> writes:
>>
>>> This patch allow the unprivileged user to mount mqueuefs in
>>> user ns.
>>>
>>> If two userns share the same ipcns,the files in mqueue fs
>>> should be seen in both these two userns.
>>>
>>> If the userns has its own ipcns,it has its own mqueue fs too.
>>> ipcns has already done this job well.
>>
>> I am a little dense. When does userspace actually mount a mqueuefs?
>> My impression was that user space never needed to mount and actually
>> never could mount a mqueuefs. MS_NO_USER isn't set so mounting a
>> mqueuefs is possible but when does it happen and why?
>>
>
> Actually the files which representative messgae queue in mqueuefs contains
> some informations,such as QSIZE,NOTIFY,SIGNO,NOTIFY_PID.
>
> My workstation is Fedora 17,mqueuefs is mounted on /dev/mqueue by default.
> So I think at lest this patch is needed by some people.
I have just confirmed that the most you can do in a mounted mqueue fs is
to create files message queues.
Given that these filesystems exist anyway I don't see a problem.
Applied thanks.
Eric
prev parent reply other threads:[~2013-01-28 7:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 3:09 [PATCH] userns: Allow the unprivileged users to mount mqueue fs Gao feng
2013-01-28 3:43 ` Eric W. Biederman
2013-01-28 6:48 ` Gao feng
2013-01-28 7:14 ` Eric W. Biederman [this message]
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=877gmxye1j.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.linux-foundation.org \
--cc=gaofeng@cn.fujitsu.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=serge.hallyn@canonical.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