Ok, that's fair enough. A wrapper module could always be written that then
in turn invokes user space. That's good enough for me although it makes for
additional overhead but I guess that is not too bad.
>All the better to keep userspace callbacks for security out of my
>kernels, for that way is ripe for problems (for specific examples why,
>see the linux-security-module mailing list archives.)
Oh, sure. There are problems. I don't deny that. But I am not too sure that
those problems outweigh the problems created by putting in huge amounts of
code into the kernel which could live outside it just as well. - IMHO the
kernel should be as small as possible rather than contain everything under
the sun just because it's easier to do that way...
Best regards,
Anton
-- "Nothing succeeds like success." - Alexandre Dumas-- Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @) Linux NTFS Maintainer / WWW: http://linux-ntfs.sf.net/ ICQ: 8561279 / WWW: http://www-stu.christs.cam.ac.uk/~aia21/- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/