Re: intercepting syscalls

[Igor Shmukler]

> > 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 ?

now, when I need someone to tell I do something wrong, I know where to go :)
-
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/