From: James Hogan <james.hogan@imgtec.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Containers <containers@lists.linux-foundation.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
<linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Andy Lutomirski <luto@amacapital.net>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] sysfs: Allow mounting without CONFIG_NET
Date: Tue, 24 Sep 2013 12:25:49 +0100 [thread overview]
Message-ID: <524176BD.9060403@imgtec.com> (raw)
In-Reply-To: <87ioxrrzb6.fsf_-_@tw-ebiederman.twitter.com>
On 23/09/13 22:41, Eric W. Biederman wrote:
>
> In kobj_ns_current_may_mount the default should be to allow the
> mount. The test is only for a single kobj_ns_type at a time, and unless
> there is a reason to prevent it the mounting sysfs should be allowed.
> Subsystems that are not registered can't have are not involved so can't
> have a reason to prevent mounting sysfs.
>
> This is a bug-fix to:
> commit 7dc5dbc879bd0779924b5132a48b731a0bc04a1e
> Author: Eric W. Biederman <ebiederm@xmission.com>
> Date: Mon Mar 25 20:07:01 2013 -0700
>
> sysfs: Restrict mounting sysfs
>
> Don't allow mounting sysfs unless the caller has CAP_SYS_ADMIN rights
> over the net namespace. The principle here is if you create or have
> capabilities over it you can mount it, otherwise you get to live with
> what other people have mounted.
>
> Instead of testing this with a straight forward ns_capable call,
> perform this check the long and torturous way with kobject helpers,
> this keeps direct knowledge of namespaces out of sysfs, and preserves
> the existing sysfs abstractions.
>
> Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
>
> That came in via the userns tree during the 3.12 merge window.
>
> Reported-by: James Hogan <james.hogan@imgtec.com>
> Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
Tested-by: James Hogan <james.hogan@imgtec.com>
Thanks
James
next prev parent reply other threads:[~2013-09-24 11:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 21:44 [REVIEW][PATCH 1/2] userns: Better restrictions on when proc and sysfs can be mounted Eric W. Biederman
2013-08-27 21:46 ` [REVIEW][PATCH 2/2] sysfs: Restrict mounting sysfs Eric W. Biederman
2013-08-28 19:00 ` Greg Kroah-Hartman
2013-09-23 10:33 ` James Hogan
2013-09-23 21:41 ` [PATCH] sysfs: Allow mounting without CONFIG_NET Eric W. Biederman
2013-09-24 11:25 ` James Hogan [this message]
2013-08-27 21:47 ` [REVIEW][PATCH 1/2] userns: Better restrictions on when proc and sysfs can be mounted Andy Lutomirski
2013-08-27 21:57 ` Eric W. Biederman
2013-09-01 4:45 ` Eric W. Biederman
2013-09-03 17:40 ` Andy Lutomirski
2013-11-02 6:06 ` Gao feng
2013-11-04 7:00 ` Janne Karhunen
2013-11-09 5:22 ` Eric W. Biederman
2013-11-08 2:33 ` Gao feng
2013-11-09 5:42 ` Eric W. Biederman
2013-11-13 7:26 ` Gao feng
2013-11-14 11:10 ` Gao feng
2013-11-14 16:54 ` Andy Lutomirski
2013-11-15 1:16 ` Gao feng
2013-11-15 4:54 ` Eric W. Biederman
2013-11-15 6:14 ` Gao feng
2013-11-15 8:37 ` Eric W. Biederman
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=524176BD.9060403@imgtec.com \
--to=james.hogan@imgtec.com \
--cc=containers@lists.linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=serge@hallyn.com \
--cc=torvalds@linux-foundation.org \
/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