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] [day] [month] [year] [list]

Message-ID: <20120329182919.GB6891@redhat.com>
Date:	Thu, 29 Mar 2012 14:29:19 -0400
From:	Dave Jones <davej@...hat.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>,
	Wu Fengguang <fengguang.wu@...el.com>,
	"Theodore Ts'o" <tytso@....edu>
Subject: Re: lockups shortly after booting in current git.

On Thu, Mar 29, 2012 at 11:23:57AM -0700, Linus Torvalds wrote:

 > That's doubly true since I see processes waiting for the journal lock,
 > but I don't actually see anything waiting for journal IO completion.
 > Did something not release the journal lock. Even banshee - that *is*
 > waiting for actual IO - seems to wait for page_writeback, which is not
 > done by the *disk* driver, but by the filesystem (end_page_writeback).
 > So that would be consistent with the ext4 changes having broken that.
 > 
 > Was there a previous post-3.3 git kernel that worked?

This is the first one I tried. (I've not been anywhere with the laptop
since 3.3 -- clearly I need to get out more). 

3.3 final worked ok though.

	Dave

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