From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Pavel Emelianov <xemul@openvz.org>
Subject: Re: [PATCH 2/2] devcgroup: fix permission check when adding entry to child cgroup
Date: Mon, 7 Jul 2008 10:48:59 -0500 [thread overview]
Message-ID: <20080707154859.GF11250@us.ibm.com> (raw)
In-Reply-To: <486F091C.8050803@cn.fujitsu.com>
Quoting Li Zefan (lizf@cn.fujitsu.com):
> # cat devices.list
> c 1:3 r
> # echo 'c 1:3 w' > sub/devices.allow
> # cat sub/devices.list
> c 1:3 w
>
> As illustrated, the parent group has no write permission to /dev/null,
> so its child should not be allowed to add this write permission,
> which is documented in Documentation/controllers/devices.txt.
>
> Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
I have no idea where that came from (but see that it was in my original
submission). Maybe I meant to do &, but that still isn't necessary.
Acked-by: Serge Hallyn <serue@us.ibm.com>
thanks,
-serge
> ---
> security/device_cgroup.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/security/device_cgroup.c b/security/device_cgroup.c
> index 1e2e28a..ddd92ce 100644
> --- a/security/device_cgroup.c
> +++ b/security/device_cgroup.c
> @@ -300,7 +300,7 @@ static int may_access_whitelist(struct dev_cgroup *c,
> continue;
> if (whitem->minor != ~0 && whitem->minor != refwh->minor)
> continue;
> - if (refwh->access & (~(whitem->access | ACC_MASK)))
> + if (refwh->access & (~whitem->access))
> continue;
> return 1;
> }
> --
> 1.5.4.rc3
prev parent reply other threads:[~2008-07-07 15:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-05 5:39 [PATCH 2/2] devcgroup: fix permission check when adding entry to child cgroup Li Zefan
2008-07-07 15:48 ` Serge E. Hallyn [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=20080707154859.GF11250@us.ibm.com \
--to=serue@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=xemul@openvz.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