linux-kernel - Re: WARN_ON at line 380 in kernel/smp.c under 2.6.32.2 + TuxOnIce + KDB

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4B60C632.5050500@tuxonice.net>
Date:	Thu, 28 Jan 2010 10:03:14 +1100
From:	Nigel Cunningham <nigel@...onice.net>
To:	Peter Zijlstra <peterz@...radead.org>
CC:	Pedro Ribeiro <pedrib@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: WARN_ON at line 380 in kernel/smp.c under 2.6.32.2 + TuxOnIce
 + KDB

Hi Peter et al.

Peter Zijlstra wrote:
> On Tue, 2009-12-22 at 19:16 +0000, Pedro Ribeiro wrote:
>> On Tue, Dec 22, 2009 at 5:20 PM, Peter Zijlstra <peterz@...radead.org> wrote:
> 
>>> If you'd enable frame pointers the strack traces would be clearer, but
>>> it looks like a bug in tux on ice, doing kmap_high() with IRQs disabled
>>> or something like that.
> 
>> I enabled frame pointers, is this more useful?
>> http://img684.imageshack.us/img684/5118/dsc01206m.jpg
>> http://img96.imageshack.us/img96/5493/dsc01207k.jpg
>> http://img33.imageshack.us/img33/7470/dsc01208lp.jpg
> 
> Those read more clearly indeed, thanks!
> 
> It really looks like what I said above, in that tux on ice is calling
> kmap() from an inappropriate context.

I've finally gotten around to looking at this problem properly, and Pete
is exactly right. I'll send a test fix to Pedro separately.

Regards,

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