linux-kernel - Re: [patch] i386: fix one case of stuck dwarf2 unwinder II

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: <44D70F42.76E4.0078.0@novell.com>
Date:	Mon, 07 Aug 2006 09:00:34 +0100
From:	"Jan Beulich" <jbeulich@...ell.com>
To:	"Chuck Ebbert" <76306.1226@...puserve.com>,
	"Andi Kleen" <ak@...e.de>
Cc:	"Jesper Juhl" <jesper.juhl@...il.com>,
	"Andrew Morton" <akpm@...l.org>, "Dave Jones" <davej@...hat.com>,
	"linux-kernel" <linux-kernel@...r.kernel.org>
Subject: Re: [patch] i386: fix one case of stuck dwarf2 unwinder II

>> Yes that's the problem. If you check for <= stext/_stext then the unwinder
>> won't catch the L6 (which is above it) and report a "stuck" again
>
>Maybe I'm being dense here, but:
>
>c0100210 t L6
>c0100212 t check_x87
>c010023a t setup_idt
>c0100257 t rp_sidt
>c0100264 t ignore_int
>c0100298 T stext
>c0100298 T _stext
>
>It looks like L6 is before _stext to me.

So it would seem to me. Nevertheless, in my opinion the proper fix is to annotate the call site
(in head.S) to specify a zero EIP as return address (which denotes the bottom of a frame).

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/