linux-kernel - Re: BUG-lockdep and freeze (was: Arrr! Linux 2.6.18)

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: <Pine.LNX.4.64.0609301748340.3952@g5.osdl.org>
Date:	Sat, 30 Sep 2006 17:51:12 -0700 (PDT)
From:	Linus Torvalds <torvalds@...l.org>
To:	Andi Kleen <ak@...e.de>
cc:	Eric Rannaud <eric.rannaud@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...e.hu>, Andrew Morton <akpm@...l.org>,
	nagar@...son.ibm.com, Chandra Seetharaman <sekharan@...ibm.com>,
	Jan Beulich <jbeulich@...ell.com>
Subject: Re: BUG-lockdep and freeze (was: Arrr! Linux 2.6.18)

On Sat, 30 Sep 2006, Linus Torvalds wrote:
> 
>  - you have an outer loop that loops around the pages (since the _kernel_ 
>    controls the stack nesting at that level). This is the loop I quoted at 
>    you.
> 
>  - you have a _separate_ "unwinder()" for each page. It only unwinds 
>    within that one page, and if the frame moves away from the page, it 
>    immediately just returns that address, but it knows that it cannot be a 
>    "valid" unwind address within that page.

Side note: it's entirely possible that the "unwinder" code shouldn't even 
try to return the address outside the page, since the first/last frame on 
a page is likely to be special (ie it's an exception/interrupt kind of 
thing), and it's entirely possible that the "page-level" loop is better at 
handling that part too.

That way you wouldn't even need to make the exception frames haev the 
dwarf info etc, because you could choose to just depend on knowing what 
the format of such a page was. But that's obviously just an implementation 
choice..

Doesn't that sound like it should be both fairly straightforward and 
reasonable?

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