From: Jeff D. <jd...@ad...> - 2003-09-04 19:50:32
|
m.a...@du... said: > Jeff, we worked out what the bug was. His old selinux used syscall > 223, which was completely uninitialized (ie. not even set to > sys_ni_syscall), hence the kernel crashed. I was having the same > problem in a different context with get_thread_area and > set_thread_area. Oops, looks like I missed that. Easily fixed, it looks like those were NULL-filled holes in sys_call_table. The system call dispatcher did range checking on the syscall number, but didn't see if the entry itself contained anything. And it looks like I missed some system calls that i386 has. Jeff |