Messages in this thread | | | Subject | Re: intercepting syscalls | From | Terje Malmedal <> | Date | Mon, 18 Apr 2005 20:56:10 +0200 |
| |
[Arjan van de Ven] >> > 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 :)
> ok i'll spice things up... I'll even suggest a better solution ;)
Hi. The promise wasn't made to me, but I'm hoping you will find a nice and clean solution:
Every so often there is bug in the kernel, by patching the syscall-table I have been able to fix bugs in ioperm and fsync without rebooting the box.
What do I do the next time I need to do something like this?
-- - Terje tm@basefarm.no - 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/
| |