calling sys_function() functions directly doesn't look right:
1. what if one was to do some accounting of the system calls. Not going
through the int 0x80 would break this.
2. what if one were to temporarily redirect some system calls to another
handler (like timetravel.o module does).
3. probably other "what-ifs".
So, it is better to ensure that either one can go through that gate as
many times as one wants or forbid it completely.
Matthew, if, as you say a specific Linux port disallows that, how are you
going to handle kernel/kmod.c and all the other occurrences where
_syscallX() is used from kernel space?
Regards,
Tigran.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/