On Fri, 2 January 2004 16:39:04 +0100, Libor Vanek wrote: > > > The code looks very nice'n'simple but it won't run on 2.6 because > mentioned hidden sys_call_table. But I can imagine that this with some > small tweaks can be integrated into 2.6 to provide generall > infrastructure for syscall hijacking when really needed. Repeat: This is a hack, nothing else. *You* need it for your thesis, so go ahead. The right solution for the problem, which is research, rather than engineering. But don't think this mess should be integrated into mainline, much less tell other people it should. *Noone* needs it for real code that is supposed to do something meaningful. Some people feel they need it, but they just haven't found the right solution yet and believe this hack to be right. It isn't. Clear enough? J$Bvr(Bn -- The competent programmer is fully aware of the strictly limited size of his own skull; therefore he approaches the programming task in full humility, and among other things he avoids clever tricks like the plague. -- Edsger W. Dijkstra - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
References:
- Syscall table AKA hijacking syscallsLibor Vanek
- Re: Syscall table AKA hijacking syscallsRagnar =?iso-8859-15?Q?Kj=F8rstad?=
- Re: Syscall table AKA hijacking syscallsLibor Vanek
- Prev by Date: Re: udev and devfs - The final word
- Next by Date: Re: [PATCH 1/2] kthread_create
- Previous by thread: Re: Syscall table AKA hijacking syscalls
- Next by thread: Re: Syscall table AKA hijacking syscalls
- Indexes:[Main][Thread]