linux-kernel - Re: [Nasty crash on boot] was Re: 2.6.19-rc2-mm2

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: <20061022223709.GA79345@muc.de>
Date:	Mon, 23 Oct 2006 00:37:09 +0200
From:	Andi Kleen <ak@....de>
To:	Andrew Morton <akpm@...l.org>
Cc:	Reuben Farrelly <reuben-lkml@...b.net>,
	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	Jan Beulich <jbeulich@...ell.com>
Subject: Re: [Nasty crash on boot] was Re: 2.6.19-rc2-mm2

> > Pid: 5, comm: ksoftirqd/1 Not tainted 2.6.19-rc2-mm2 #1
> > RIP: 0010:[<ffffffff80267849>]  [<ffffffff80267849>] dump_trace+0x3a9/0x422

This might have been related to the uninitialized cpu variable which
made the interrupt stacks uninitialized
Another patch broke that and gcc even warned about it but I only fixed  
it today.

It was only in -mm* for a short time too.

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