linux-kernel - Re: [patch] i386: fix stuck unwind into kernel thread

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] [day] [month] [year] [list]

Message-Id: <200608071011.31473.ak@suse.de>
Date:	Mon, 7 Aug 2006 10:11:31 +0200
From:	Andi Kleen <ak@...e.de>
To:	"Jan Beulich" <jbeulich@...ell.com>
Cc:	"Chuck Ebbert" <76306.1226@...puserve.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [patch] i386: fix stuck unwind into kernel thread

On Monday 07 August 2006 10:07, Jan Beulich wrote:
> >>> Chuck Ebbert <76306.1226@...puserve.com> 06.08.06 20:56 >>>
> >We cannot unwind past kernel_thread_helper.
> 
> Just as mentioned before - we shouldn't add endless special cases to the code that interprets the unwind
> information, but rather fix the unwind information so that it properly reflect the actual state. Like in the
> other case, the piece of code should be properly annotated, which would require it to be moved into
> an assembly file (it escapes me why code like that was ever placed in a C file).

I can do that.

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