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: <20120329233506.GG13970@thunk.org>
Date:	Thu, 29 Mar 2012 16:35:06 -0700
From:	Ted Ts'o <tytso@....edu>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Dave Jones <davej@...hat.com>,
	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:04:50PM -0700, Linus Torvalds wrote:
> On Thu, Mar 29, 2012 at 3:54 PM, Dave Jones <davej@...hat.com> wrote:
> >
> > 90 mins of 2x kernel builds in parallel along with
> > 3x fsx runs. then my battery ran out.
> >
> > looks like we have a winner.
> 
> Ok, let's revert it. Do you want to write the description of what
> happened, or should I just do it?

How about this:

Commit b43d17f31 (ext4: don't release page refs in ext4_end_bio) is
apprently causing system lockups for a system using a LUKS backed
system partition.  This luckup can be reproduced by running a make -j8
kernel compile in parallel with fsx.

Since the commit in question was fixing a rare and fairly exotic race,
and the lockup was found fairly quickly, it is being reverted as a
regression fix.

						- Ted

P.S.  I've been using 3.3 + the ext4 development tree on my laptop for
a while now, with a LUKS-encrypted+LVM setup on both a SSD and HDD on
a Ubuntu 10.04 based system.  I've not noticed the problem that Dave
is seeing under normal use.  So I'm wondering what was triggering it
on what should have been an idle desktop system in his case.  But this
is definitely a case where we should revert first, and ask questions
later.

Dave, thanks for noticing and reporting this!

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