linux-kernel - Re: [-rc7 regression] Block IO/VFS/ext3/timer spinlock lockup?

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]

Date:	Thu, 14 Feb 2013 15:54:24 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Jens Axboe <axboe@...nel.dk>,
	Alexander Viro <viro@....linux.org.uk>,
	Theodore Ts'o <tytso@....edu>, "H. Peter Anvin" <hpa@...or.com>
Subject: Re: [-rc7 regression] Block IO/VFS/ext3/timer spinlock lockup?

> CPU0 appears to be idle:
> 
> [  118.510000] Call Trace:
> [  118.510000]  [<7900844b>] cpu_idle+0x86/0xb4
> [  118.510000]  [<792a91df>] rest_init+0x103/0x108
> [  118.510000]  [<794558cc>] start_kernel+0x2c7/0x2cc

So, I've done a partial bisection, the breakage appears to have 
gone upstream between v3.8-rc3 and v3.8-rc4.

This roughly coincides with the time frame when I first saw 
these lockups pop up, so in that sense it's a plausible result - 
but there weren't all that many commits in -rc4 and none looks 
really suspicious, so this might be one of those non-bisectable 
bugs.

( Later today I'll try to finish the bisection just in case it
  results in something useful. )

Thanks,

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