public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ted Ts'o" <tytso@mit.edu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Jones <davej@redhat.com>,
	Wu Fengguang <fengguang.wu@intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: lockups shortly after booting in current git.
Date: Thu, 29 Mar 2012 16:35:06 -0700	[thread overview]
Message-ID: <20120329233506.GG13970@thunk.org> (raw)
In-Reply-To: <CA+55aFxwfzRniiTRVysvjnSaMYXQwrk8O8iQ-xdy1DXYxeL+cw@mail.gmail.com>

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@redhat.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!


  reply	other threads:[~2012-03-29 23:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-29 15:55 lockups shortly after booting in current git Dave Jones
2012-03-29 18:23 ` Linus Torvalds
2012-03-29 18:29   ` Dave Jones
     [not found] ` <CA+55aFxOcMt_mcr+ZYwc-SpKbROnh4Gn7jqrFY_SZcBy1Ev7Qw@mail.gmail.com>
     [not found]   ` <20120329182632.GA6891@redhat.com>
2012-03-29 18:36     ` Linus Torvalds
2012-03-29 19:53       ` Dave Jones
2012-03-29 20:10         ` Linus Torvalds
2012-03-29 20:26           ` Dave Jones
2012-03-29 20:38             ` Linus Torvalds
2012-03-29 20:39             ` Ted Ts'o
2012-03-29 20:59               ` Linus Torvalds
2012-03-29 21:12                 ` Dave Jones
2012-03-29 21:45                   ` Ted Ts'o
2012-03-29 21:49                     ` Dave Jones
2012-03-29 21:52                       ` Linus Torvalds
2012-03-29 22:54                         ` Dave Jones
2012-03-29 23:04                           ` Linus Torvalds
2012-03-29 23:35                             ` Ted Ts'o [this message]
2012-03-29 23:25                         ` Ted Ts'o
2012-03-29 21:52                     ` Dave Jones

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120329233506.GG13970@thunk.org \
    --to=tytso@mit.edu \
    --cc=davej@redhat.com \
    --cc=fengguang.wu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox