On Tue, 5 Jun 2001, Chris Wright wrote: > The init funcition can leave your sys_calls registered even if the > register_security call fails. Is that intentional? Simlarly, the exit > function sets the sys_calls to NULL. Shouldn't they be sys_ni_syscall > instead? Actually, I'll have to take the blame for these errors in the SELinux module. Yes, you are correct that these are errors. -- Stephen D. Smalley, NAI Labs ssmalleyat_private _______________________________________________ linux-security-module mailing list linux-security-moduleat_private http://mail.wirex.com/mailman/listinfo/linux-security-module
This archive was generated by hypermail 2b30 : Wed Jun 06 2001 - 06:01:47 PDT