From: Keith Owens <kaos@ocs.com.au>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] [PATCH] C exceptions in kernel
Date: Sat, 23 Feb 2002 23:26:52 +1100 [thread overview]
Message-ID: <25097.1014467212@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Sat, 23 Feb 2002 05:11:36 CDT." <200202231011.g1NABaU10984@devserv.devel.redhat.com>
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.
next prev parent reply other threads:[~2002-02-23 12:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1014437101.26721.linux-kernel2news@redhat.com>
2002-02-22 21:12 ` Dan Aloni
2002-02-22 21:28 ` Davide Libenzi
2002-02-22 22:10 ` Richard B. Johnson
2002-02-22 22:34 ` David B. Stevens
2002-02-22 22:48 ` Davide Libenzi
2002-02-23 3:37 ` Edgar Toernig
2002-02-23 10:11 ` Pete Zaitcev
2002-02-23 12:26 ` Keith Owens [this message]
2002-02-23 12:50 ` Pete Zaitcev
2002-02-23 23:07 ` Jes Sorensen
2002-02-23 23:40 ` Keith Owens
2002-02-24 1:02 ` Jes Sorensen
2002-02-24 23:45 ` Richard Gooch
2002-02-23 23:50 ` Bill Huey
2002-02-24 1:31 ` Davide Libenzi
2002-02-24 2:55 ` Bill Huey
2002-02-23 15:13 ` Felix von Leitner
2002-02-23 15:21 ` bert hubert
2002-02-23 17:47 ` Alexander Viro
2002-02-23 18:21 ` bert hubert
2002-02-23 18:31 ` Larry McVoy
2002-02-23 18:38 ` bert hubert
2002-02-23 19:12 ` Kurt Ferreira
2002-02-23 23:05 ` Jes Sorensen
2002-02-23 16:05 ` Dan Aloni
2002-02-23 16:22 ` Larry McVoy
2002-02-23 17:07 ` bert hubert
2002-02-23 17:00 ` Dan Aloni
2002-02-23 17:52 ` Francois Romieu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=25097.1014467212@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=zaitcev@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®