From: Bill Irwin <bill.irwin@oracle.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Bill Irwin <bill.irwin@oracle.com>,
Andi Kleen <andi@firstfloor.org>,
Chuck Ebbert <cebbert@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Wanted: simple, safe x86 stack overflow detection
Date: Wed, 28 Feb 2007 15:45:24 -0800 [thread overview]
Message-ID: <20070228234524.GC10643@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0703010035590.23355@yvahk01.tjqt.qr>
On Feb 28 2007 15:20, Bill Irwin wrote:
>> I don't know about the rest of the world, but halting the system in the
>> case of memory corruption sounds like an extremely good idea to me.
On Thu, Mar 01, 2007 at 12:36:47AM +0100, Jan Engelhardt wrote:
> Just because a rather "unimportant" driver (e.g. parport) might oops
> thanks to a now-invalid address after memory corruption, I'd still like
> to shutdown the system normally - which should be possible when not
> using parport after said corruption.
Panic on oops/bug is sysctl-activated as things now stand, so you're
all set.
-- wli
next prev parent reply other threads:[~2007-02-28 23:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-28 14:27 Wanted: simple, safe x86 stack overflow detection Chuck Ebbert
2007-02-28 16:31 ` Thiago Galesi
2007-02-28 20:41 ` Andi Kleen
2007-02-28 23:20 ` Bill Irwin
2007-02-28 23:36 ` Jan Engelhardt
2007-02-28 23:45 ` Bill Irwin [this message]
2007-03-04 1:50 ` Bill Irwin
2007-03-06 18:59 ` Chuck Ebbert
2007-03-06 19:43 ` Hugh Dickins
2007-03-06 20:34 ` Bill Irwin
2007-03-07 4:28 ` Arjan van de Ven
2007-03-07 6:44 ` Bill Irwin
2007-03-07 12:34 ` Arjan van de Ven
2007-03-07 14:48 ` Bill Irwin
2007-03-07 15:04 ` Arjan van de Ven
2007-03-08 7:43 ` Avi Kivity
2007-03-19 20:53 ` Eric W. Biederman
2007-03-06 20:06 ` Bill Irwin
2007-03-05 1:18 ` Arnd Bergmann
2007-03-05 12:39 ` Andi Kleen
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=20070228234524.GC10643@holomorphy.com \
--to=bill.irwin@oracle.com \
--cc=andi@firstfloor.org \
--cc=cebbert@redhat.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
/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