Messages in this thread | | | Subject | Re: intercepting syscalls | From | Arjan van de Ven <> | Date | Mon, 18 Apr 2005 16:59:37 +0200 |
| |
> Intercepting system call table is an elegant way to solve many > problems.
I think I want to take offence to this. It's the worst possible way to solve many problems, especially since almost everyone who did this to get anything done until today got it wrong.
It's about locking. Portability. Stability
but also about doing things at the right layer. The syscall layer is almost NEVER the right layer.
Can you explain exactly what you are trying to do (it's not a secret I assume, kernel modules are GPL and open source after all, esp such invasive ones) and I'll try to tell you why it's wrong to do it at the syscall intercept layer... deal ?
Greetings, Arjan van de Ven
- 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/
| |