On Mon, Aug 26, 2013 at 7:29 PM, Casey Schaufler <ca...@schaufler-ca.com> wrote: > On 8/6/2013 3:36 PM, Kees Cook wrote: >> On Tue, Aug 6, 2013 at 3:25 PM, Casey Schaufler <ca...@schaufler-ca.com> >> wrote: >>> On 8/5/2013 11:30 PM, Kees Cook wrote: >>>> On Thu, Jul 25, 2013 at 11:52 PM, Casey Schaufler <ca...@schaufler-ca.com> >>>> wrote: >>>>> The /proc/*/attr interfaces are given to one LSM. This can be >>>>> done by setting CONFIG_SECURITY_PRESENT. Additional interfaces >>>>> have been created in /proc/*/attr so that each LSM has its own >>>>> named interfaces. The name of the presenting LSM can be read from >>>> For me, this is one problem that was bothering me, but it was a cosmetic >>>> one that I'd mentioned before: I really disliked the /proc/$pid/attr >>>> interface being named "$lsm.$file". I feel it's important to build >>>> directories in attr/ for each LSM. So, I spent time to figure out a way to >>>> do this. This patch changes the interface to /proc/$pid/attr/$lsm/$file >>>> instead, which I feel has a much more appealing organizational structure. >>> I will confess that the reason I went with <lsm>.current instead of >>> <lsm>/current was that the former was easier to implement. >> Yeah, that's totally fine. It wasn't very obvious (to me) how to >> implement this initially, so no problem at all. I'm glad there was >> something more than bug fixes I could contribute to this series. :) > > Oh dear. I'm rebasing for 3.12 and the macros don't generate compiling > code any longer. It seems that, among other things, readdir is no longer > a member of file_operations.
Agh. I will take a look. -Kees -- Kees Cook Chrome OS Security -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
