Re: The disappearing sys_call_table export.

Werner Almesberger
2003-05-10T18:13:59Z

Arjan van de Ven wrote:
> The only solution for this is to check/audit/log things after the ONE
> copy. Eg not by overriding the syscall but inside the syscall.

Well, not exactly the _only_ one. Inferior alternatives include

- tracking all user memory accesses, and protecting those pages
against modifications by other processes (but this adds a
deadlock risk)

- like above, but copy all such data to/from a user space area
that is then protected

- like above, but use kernel space instead, then use
set_fs(KERNEL_DS)

Which probably just proves that there are always more painful ways
to do things :-)

- Werner

--
_________________________________________________________________________
/ Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/