From: Theodore Tso <tytso@MIT.EDU>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
Arjan van de Ven <arjan@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@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 16:20:38 -0500 [thread overview]
Message-ID: <20090114212038.GJ6222@mit.edu> (raw)
In-Reply-To: <1231961377.14825.51.camel@laptop>
On Wed, Jan 14, 2009 at 08:29:37PM +0100, Peter Zijlstra wrote:
> > 38d47c1b7075bd7ec3881141bb3629da58f88dab is first bad commit
> > commit 38d47c1b7075bd7ec3881141bb3629da58f88dab
> > Author: Peter Zijlstra <a.p.zijlstra@chello.nl>
> > Date: Fri Sep 26 19:32:20 2008 +0200
> >
> > futex: rely on get_user_pages() for shared futexes
> >
> > On the way of getting rid of the mmap_sem requirement for shared futexes,
> > start by relying on get_user_pages().
> >
> > Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
> > Acked-by: Nick Piggin <nickpiggin@yahoo.com.au>
> > Signed-off-by: Ingo Molnar <mingo@elte.hu>
> >
> However does a futex change make ext3 crap its pants?
I agree, this doesn't make much sense. I've looked at the patch, and
I don't see how this would cause an ext3 orphaned-inode list handling
problem
Are you sure the bisect was done correctly? Have you tried reverting
that one commit, or otherwise conclusively shown that a kernel with
this commit fails, and one without this commit works just fine?
- Ted
next prev parent reply other threads:[~2009-01-14 21:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090110003645.GA16107@linux-os.sc.intel.com>
2009-01-14 0:48 ` kernel BUG at fs/ext/super.c:428 Andrew Morton
2009-01-14 1:44 ` Theodore Tso
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:29 ` Peter Zijlstra
2009-01-14 19:38 ` Pallipadi, Venkatesh
2009-01-14 19:42 ` Peter Zijlstra
2009-01-14 19:48 ` Pallipadi, Venkatesh
2009-01-14 21:20 ` Theodore Tso [this message]
2009-01-21 20:10 ` Pallipadi, Venkatesh
2009-01-24 7:36 ` Peter Zijlstra
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=20090114212038.GJ6222@mit.edu \
--to=tytso@mit.edu \
--cc=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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).