Messages in this thread | | | Date | Wed, 28 Feb 2007 15:45:24 -0800 | From | Bill Irwin <> | Subject | Re: Wanted: simple, safe x86 stack overflow detection |
| |
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 - 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/
| |