On Sat, 23 Feb 2002 05:11:36 -0500,
Pete Zaitcev <zaitcev@redhat.com> wrote:
>>> The attached patch implements C exceptions in the kernel,
Kernel code already has exception tables to handle invalid addresses,
invalid opcodes etc. See copy_to_user and wrmsr_eio for examples.
Apart from that, the kernel code assumes that it knows what it is doing
and does not need exceptions, any unexpected exceptions quite correctly
fall into the oops handler.
The kernel model is "get it right the first time, so we don't need
exception handlers". You have not given any reason why the existing
mechanisms are failing.
>do we support setjump/longjump
>in kernel? The patch as I saw it does reimplement a similar thing
>(check out its assembler fragments).
Standard kernel code does not support setjmp/longjmp. AFAIK the only
code that does is the kdb patch where I need the extra protection, when
kdb is entered it is a fair bet that something has already gone wrong.
-
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/
This archive was generated by hypermail 2b29 : Sat Feb 23 2002 - 21:00:50 EST