On Fri, 26 Sep 2008 00:31:09 +1000, James Morris said:
- Francis asked for a much-secure or safer workaround to the issue.
Given that the driver is messing with kernel security, is also broken in
its use of a security API, and not maintained, I'm certainly not going to
recommend its continued use in this context.
Given the fact it's a kernel BUG, I wonder if the *real* issue isn't
that the driver doesn't support SELinux, but that it doesn't understand
the expanded more-than-32-bits capabilities in recent kernels, causing
something to overlay something it shouldn't have...