On Thu, 20 Apr 2000, Borislav Deianov wrote:
> Modifying sys_call_table from a module works fine but is architecture
> specific (I'm told) and gets intersting when two modules try to
> intercept the same system call.
this interesting part can be resolved rather straightforward by providing
an (exported) read-write spinlock that is taken for read on each system
call and write by those wishing to modify sys_call_table[]. (this is not
nice because of the effort of taking even a read spinlock on each syscall)
> There was a patch a while ago that
> provided infrastructure for doing this properly, at the expense of
> some overhead. The problem with that is that it'll only be useful if
> it gets into the kernel and everybody uses it but it won't because of
> the overhead.
>
agree.
Regards,
Tigran
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Apr 23 2000 - 21:00:17 EST