> hijacks syscall entries in the sys_call_table as well, because we
> want it to work as a module and not require patching the kernel. Our
> solution to the module unload race on syscall de-hijacking is simple,
> splitting the system call hijacking code into a single small module
> which once loaded cannot be unloaded.
So your small module can export a function called
patch_syscall(NR_foo, function);
Now you can put the arch specific syscall patching code into your small
common module and its cleaner anyway ?
Alan
-
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/
This archive was generated by hypermail 2b29 : Sun Apr 07 2002 - 22:00:20 EST