On Sep 7 2007 14:28, Andreas Gruenbacher wrote:
Well, that's because of the AppArmor patches; AppArmor requires an additional struct vfsmnt parameter.
Have a look at http://freshmeat.net/p/multiadm/ how I worked around this. (Though I am not sure apparmor likes taking a NULL vfsmnt arg........if not, it really SHOULD.)
AppArmor cannot compute the pathnames of files without a proper vfsmnt parameter, so passing NULL effectively disables AppArmor for this specific notify_change() call. Without knowing which file is changed, what triggers the change, and why, it is somewhat hard to tell whether passing NULL is okay.
I mean: at least it should not oops when passed NULL. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org