linux-kernel - Re: boot failure, "DWARF2 unwinder stuck at 0xc0100199"

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <44EADA09.76E4.0078.0@novell.com>
Date:	Tue, 22 Aug 2006 10:18:49 +0200
From:	"Jan Beulich" <jbeulich@...ell.com>
To:	"Andrew Morton" <akpm@...l.org>, "Andi Kleen" <ak@...e.de>
Cc:	"J. Bruce Fields" <bfields@...ldses.org>,
	<linux-kernel@...r.kernel.org>,
	"Randy.Dunlap" <rdunlap@...otime.net>
Subject: Re: boot failure, "DWARF2 unwinder stuck at 0xc0100199"

>> Has anyone even tried to reproduce Bruce's crash?
>
>I looked at it a bit, but it puzzles me. The chaining for the interrupt stacks
>on i386 -- which is what seems to be corrupted here -- shouldn't have changed at all 
>by the unwinder changes.

Not necessarily:

	if (UNW_SP(&info))
		stack = (void *)UNW_SP(&info);

is rather fragile - the minimum extra protection here should be to only use
UNW_SP() for the continuation stack pointer if it actually points into kernel
space (as is being done in one of the 2.6.19 patches), ...

>I suspect it would crash without unwinder too. Bruce, do you get the 
>same crash when you boot with "call_trace=old" ? 

... but of course I continue to agree that doing things like

	addr = *stack++;

in the legacy stack trace code cannot be good, given that this code
generally is expected to run when things are already bad in some way.

Jan
-
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/