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: <200609302357.06215.ak@suse.de>
Date:	Sat, 30 Sep 2006 23:57:06 +0200
From:	Andi Kleen <ak@...e.de>
To:	Linus Torvalds <torvalds@...l.org>
Cc:	Ingo Molnar <mingo@...e.hu>, Eric Rannaud <eric.rannaud@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	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)

> 
> It could - and _should_ dammit! - do some basic sanity tests like "is the 
> thing even in the same stack page"? But nooo... It seems _designed_ to be 
> fragile and broken.

That wouldn't work with interrupt stacks.

The old unwinder code had a state machine to deal with them,
but it was distingustingly complicated (there are nasty corner cases 
where you can be in multiple interrupt stacks nested). I'm not
sure we would have really wanted to retain that.

What it does is to do __get_user for the stack values and it has the 
unwind tables in the executable as sanity check, so in some sense it is 
more reliable than the old code.

BTW again let me repeat this particular issue wasn't in the unwinder
itself, but just in the fallback-to-old code which didn't do enough
sanity checks. So you can say it's not the new unwinder that
crashed, but the old one here. I'll add more.

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