Re: How to intercept a sys call.
- From: "David Schwartz" <davids@xxxxxxxxxxxxx>
- Date: Sat, 24 Dec 2005 13:40:35 -0800
<phil-news-nospam@xxxxxxxx> wrote in message
news:dojmt611vpl@xxxxxxxxxxxxxxxxxxxx
> On Wed, 21 Dec 2005 13:14:50 -0800 David Schwartz <davids@xxxxxxxxxxxxx>
> wrote:
> | The alternative is to add whatever functionality your module was
> going
> | to provide to the kernel, perhaps in the form of a hook specifically for
> | your module.
> There has to be something equivalent to a system call table that takes the
> syscall index and gets to the proper kernel sys_* function. He just needs
> to track down what that is (not expect us to do it for him).
There is something equivalent to a system call table; however, it is not
safe to modify it. In fact, the kernel developers explicitly state that
doing so is broken, their code doesn't support it, and there are known
scenarios where it can break horribly.
DS
.
- References:
- How to intercept a sys call.
- From: Mozis
- Re: How to intercept a sys call.
- From: Peter T. Breuer
- Re: How to intercept a sys call.
- From: Perianayagam Somasundaram
- Re: How to intercept a sys call.
- From: Mozis
- Re: How to intercept a sys call.
- From: David Schwartz
- Re: How to intercept a sys call.
- From: phil-news-nospam
- How to intercept a sys call.
- Prev by Date: Re: Want to know something about mlock or shmctl via SHMLOCK
- Next by Date: Re: Wanted: serial driver (RS232) emulation on LAN
- Previous by thread: Re: How to intercept a sys call.
- Next by thread: Re: How to intercept a sys call.
- Index(es):
Relevant Pages
|
