| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20071031092803.0048d5d6@laptopd505.fenrus.org> Date: Wed, 31 Oct 2007 09:28:03 -0700 From: Arjan van de Ven <arjan@...radead.org> To: Steven Rostedt <rostedt@...dmis.org> Cc: LKML <linux-kernel@...r.kernel.org>, Linus Torvalds <torvalds@...ux-foundation.org>, Andrew Morton <akpm@...ux-foundation.org>, Ingo Molnar <mingo@...e.hu>, Christoph Hellwig <hch@...radead.org>, Daniel Walker <dwalker@...sta.com> Subject: Re: [PATCH] dump_stack on panic On Wed, 31 Oct 2007 11:00:56 -0400 (EDT) Steven Rostedt <rostedt@...dmis.org> wrote: > > I've had too many issues in development where I hit a panic and it > gives me nothing to tell me why. > > At the very least, we should have a dump_stack in areas that are > usually caused by kernel bugs. For example, killing an interrupt > handler. > here's the deal.... the killing of an interrupt handler because of an oops THEN causes a panic. If you dump stack AGAIN, you have 2 stack traces, with the first one being the real good one, and the second one being.. well more crappy... so you proposal just dropped the good stacktrace off the screen in favor of a worse one... -- If you want to reach me at my work email, use arjan@...ux.intel.com For development, discussion and tips for power savings, visit http://www.lesswatts.org - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists