Re: Maintaining LSM modules

Previous message: Greg KH: "Re: Maintaining LSM modules"
In reply to: Stephen Smalley: "Re: Maintaining LSM modules"
Next in thread: Seth Arnold: "Re: Maintaining LSM modules"
Reply: Seth Arnold: "Re: Maintaining LSM modules"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

chrisat_private

* Stephen Smalley (sdsat_private) wrote:
> 
> I don't think that you need to export the dummy functions.  A security
> module can save a reference to the dummy operations by saving the original
> security_ops pointer prior to registering itself.  The SELinux module does
> this as part of its support for stacking with either the dummy or
> capabilities modules.  See the usage of original_ops and secondary_ops in
> the SELinux module.  Notice that the SELinux module can always safely call
> secondary_ops.

I think this is useful, however it doesn't really generalize, does it?
For modules that can be stacked, the current security_ops may not be
the dummy stubs.

cheers,
-chris
_______________________________________________
linux-security-module mailing list
linux-security-moduleat_private
http://mail.wirex.com/mailman/listinfo/linux-security-module