Messages in this thread | | | Date | Sat, 10 May 2003 15:26:27 -0300 | From | Werner Almesberger <> | Subject | Re: The disappearing sys_call_table export. |
| |
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/____________________________________________/ - 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/
| |