Syscall table AKA hijacking syscalls
From: Libor Vanek
Date: Fri Jan 02 2004 - 08:01:53 EST
Hi,
I'm writing some project which needs to hijack some syscalls in VFS
layer. AFAIK in 2.6 is this "not-wanted" solution (even that there are
some very nasty ways of doing it - see
http://mail.nl.linux.org/kernelnewbies/2002-12/msg00266.html )
Also I've found out that Linus stated that intercepting syscalls is "bad
thing" (load module a, load module b, unload module b => crash) but I
think that there are some very good reasons (and ways) to do it (see
http://syscalltrack.sourceforge.net ). My main reason to do it is that I
want my GPLed module to be able to modify some VFS syscalls without
patching and recompiling whole kernel and rebooting the machine.
So what is proper (Linus recommanded) way to do such a things? Create
patches for specific syscalls like "if this_module_installed then
call_this_function;" or try to force things like syscalltrack to go into
vanilla kernel some time? Because what I've found out there are more
projects which suffer from this restriction.
--
Libor Vanek
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/