[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47DA9FC2.7060405@openvz.org>
Date: Fri, 14 Mar 2008 18:54:42 +0300
From: Pavel Emelyanov <xemul@...nvz.org>
To: "Serge E. Hallyn" <serue@...ibm.com>
CC: Greg KH <greg@...ah.com>, James Morris <jmorris@...ei.org>,
lkml <linux-kernel@...r.kernel.org>,
linux-security-module@...r.kernel.org,
Stephen Smalley <sds@...ch.ncsc.mil>,
Casey Schaufler <casey@...aufler-ca.com>
Subject: Re: [RFC] cgroups: implement device whitelist lsm (v2)
Serge E. Hallyn wrote:
> Quoting Pavel Emelyanov (xemul@...nvz.org):
>> [snip]
>>
>>>> My main question was why was that file in the kernel/ directory?
>>>> Shouldn't that also be in the security/ directory?
>>> I'm using cgroups to track the tasks which should have their device
>>> permissions restricted. Right now cgroups are all under kernel/.
>> No. Memory cgroup is under mm/ :)
>
> Ah.
>
> Guess it could all go under security/. Should it still go there even if
> we make it not use lsm?
Sure it can - security/ is in obj-y regardless of whether the
SECURITY itself is on or off :)
>>>> And to be honest, I didn't really look at it at all other than the
>>>> diffstat to make sure you weren't messing with the kobj_map stuff
>>>> anymore :)
>>>>
>>>> thanks,
>>>>
>>>> greg k-h
>>>> --
>>>> To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
>>>> the body of a message to majordomo@...r.kernel.org
>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists