linux-kernel - Re: [BUG] 2.6.23-rc3-mm1 Oops: Machine check, sig: 7 [#1]

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: <1187854930.5972.11.camel@localhost.localdomain>
Date:	Thu, 23 Aug 2007 09:42:10 +0200
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [BUG] 2.6.23-rc3-mm1 Oops: Machine check, sig: 7 [#1]

> 
> It would be great if you could fix that wordwrapping problem.
> 
> Dunno, it beats me.  powerpc booted OK for me.  Ben, have you been playing
> around in powerpc mmap code?  How come the oops claims it died at
> kernel_execve+0x8/0x14 but the call trace points up into the vma management
> code?

I haven't changed anything that would cause such a symptom in the VMA
code... The machine check looks to me like we are accessing a stale
pointer that happens to correspond to some part of IO space that is
mapped but not responding (like PCI PIO space).

I'm travelling (and quite sick too) right now, so I can't really do much
about it at this stage. But it happens early enough that putting a
printk in vma_link_rb() to printk the various pointers involved before
dereferencing them might help.

Cheers,
Ben.

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