|Main Archive Page > Month Archives > linux-security-module archives|
Quoting Hao Xu (email@example.com):
> Serge E. Hallyn wrote:
> >Given that you are the author of the three modules you want to stack, it
> >really shouldn't be.
> >Define a convention for your three modules. I.e. always point
> > tsk->security = kmalloc(3*sizeof(void *), GFP_KERNEL);
> >where by convention each module knows which of the three pointers it
> >uses to attach its own data to.
> It's a good idea to use convention for the modules to stack, but I think
> conventions make things less generic, I'm still thinking about a
> generic stacker module that can accomodate arbitrary secondary module
Again, please let me know if you port www.sf.net/projects/lsm-stacker to the latest kernel. I can add you as an admin or just upload your patch.
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html