linux-kernel - Re: lockups shortly after booting in current git.

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: <20120329203926.GA13970@thunk.org>
Date:	Thu, 29 Mar 2012 13:39:26 -0700
From:	Ted Ts'o <tytso@....edu>
To:	Dave Jones <davej@...hat.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Wu Fengguang <fengguang.wu@...el.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: lockups shortly after booting in current git.

On Thu, Mar 29, 2012 at 04:26:19PM -0400, Dave Jones wrote:
> 
> I'll go back to trying the bisect now that I know how to reproduce it quickly.
> Do you think it might be worth restricting the bisect to fs/ ?
> Or shall I just do the whole tree bisect from 3.3 ?

I'd suggest restricting the bisect to fs/ first, and if that comes up
with something non-sensical, you can always use the good/bad data
points for a whole tree bisect.

One commit that you might want to try testing is b43d17f31^, and see
whether that works.  One potential commit that might be suspicious is
b43d17f31 given the stack trace shows one process apparently waiting
on PageWriteback.

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