linux-kernel - Re: Was: 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: <200608310941.40076.ak@suse.de>
Date:	Thu, 31 Aug 2006 09:41:40 +0200
From:	Andi Kleen <ak@...e.de>
To:	"Jan Beulich" <jbeulich@...ell.com>
Cc:	"Badari Pulavarty" <pbadari@...il.com>,
	"J. Bruce Fields" <bfields@...ldses.org>,
	petkov@...h.uni-muenster.de, akpm@...l.org,
	"lkml" <linux-kernel@...r.kernel.org>
Subject: Re: Was: boot failure, "DWARF2 unwinder stuck at 0xc0100199"

On Thursday 31 August 2006 09:35, Jan Beulich wrote:
> Andi submitted a fix for this to Linus, but that's post-rc5. Jan

I assume you mean the fallback validation fix. Linus unfortunately
didn't merge any of my new patches yet :/

But did you ever work out why the stack backtrace completely restarted? 
I never got this. In theory the RSP gotten out of the unwind
context and used for the fallback should have been already near the end
and the old unwinder shouldn't have found much.

-Andi

P.S.: Badari, we worked out your kernel_math_context trace too:
that one is actually a gcc bug related to dubious unwind tables generated
for noreturn calls (in your case do_exit). We were still discussing the best 
workaround for that one.

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