From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: Theodore Tso <tytso@mit.edu>,
Arjan van de Ven <arjan@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>,
Nick Piggin <nickpiggin@yahoo.com.au>
Subject: Re: kernel BUG at fs/ext/super.c:428
Date: Wed, 14 Jan 2009 20:42:49 +0100 [thread overview]
Message-ID: <1231962169.14825.54.camel@laptop> (raw)
In-Reply-To: <20090114193844.GA18436@linux-os.sc.intel.com>
On Wed, 2009-01-14 at 11:38 -0800, Pallipadi, Venkatesh wrote:
> > > Below is the result of full bisect
> > > futex: rely on get_user_pages() for shared futexes
> > However does a futex change make ext3 crap its pants?
> >
> > Is there anything more to it than start the machine, and reboot?
>
> Just system startup and reboot is enough to reproduce the problem. And 100%
> reproducible. So, does seem to be any timing involved either.
That's very odd indeed, non of my test systems nor Ingo's ever triggered
this, and that patch has been in -tip for a rather long time.
CommitDate: Tue Sep 30 12:35:20 2008 +0200
That's 3.5 months of test time.. most curious. What kind of userland do
you have that triggers this?
next prev parent reply other threads:[~2009-01-14 19:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-10 0:36 kernel BUG at fs/ext/super.c:428 Pallipadi, Venkatesh
2009-01-14 0:48 ` Andrew Morton
2009-01-14 1:44 ` Theodore Tso
2009-01-14 2:48 ` Arjan van de Ven
2009-01-14 2:48 ` Arjan van de Ven
2009-01-14 4:40 ` Theodore Tso
2009-01-14 19:16 ` Pallipadi, Venkatesh
2009-01-14 19:16 ` Pallipadi, Venkatesh
2009-01-14 19:29 ` Peter Zijlstra
2009-01-14 19:38 ` Pallipadi, Venkatesh
2009-01-14 19:42 ` Peter Zijlstra [this message]
2009-01-14 19:48 ` Pallipadi, Venkatesh
2009-01-14 21:20 ` Theodore Tso
2009-01-21 20:10 ` Pallipadi, Venkatesh
2009-01-21 20:10 ` Pallipadi, Venkatesh
2009-01-24 7:36 ` Peter Zijlstra
2009-01-24 7:36 ` Peter Zijlstra
2009-01-26 16:39 ` Darren Hart
2009-01-26 16:39 ` Darren Hart
2009-01-26 16:46 ` Peter Zijlstra
2009-01-26 17:12 ` Darren Hart
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=1231962169.14825.54.camel@laptop \
--to=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=tytso@mit.edu \
--cc=venkatesh.pallipadi@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.