From: Nick Bowler <nbowler@elliptictech.com>
To: Ted Ts'o <tytso@mit.edu>,
linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [PATCH -BUGFIX] Re: BUG in ext4 with 2.6.37-rc1
Date: Wed, 3 Nov 2010 14:22:29 -0400 [thread overview]
Message-ID: <20101103182229.GA8766@elliptictech.com> (raw)
In-Reply-To: <20101103181412.GH25614@thunk.org>
On 2010-11-03 14:14 -0400, Ted Ts'o wrote:
> On Tue, Nov 02, 2010 at 04:20:13PM -0400, Nick Bowler wrote:
> > The following BUG occurred today while compiling gcc, with 2.6.37-rc1+.
> > More precisely, commit 7fe19da4ca38 ("preempt: fix kernel build with
> > !CONFIG_BKL") with http://permalink.gmane.org/gmane.linux.nfs/36521
> > applied on top. It basically took out the whole system.
>
> Hi Nick,
>
> How easily can you reproduce this bug? I'm pretty sure I know what
> caused it, but it's always good to get confirmation that a patch
> addresses the reported bug. If it happens to you fairly often, can
> you try out this patch and let me know whether it fixes the bug for
> you?
I only encountered it the one time, but I haven't tried compiling gcc
since it blew up the first time (there seems to be no problem compiling
linux, for instance). I will try it again now with and without the
patch.
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
next prev parent reply other threads:[~2010-11-03 18:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 20:20 BUG in ext4 with 2.6.37-rc1 Nick Bowler
2010-11-03 18:14 ` [PATCH -BUGFIX] " Ted Ts'o
2010-11-03 18:22 ` Nick Bowler [this message]
2010-11-03 20:53 ` Nick Bowler
2010-11-07 21:21 ` Ted Ts'o
2010-11-07 22:53 ` Tony Vroon
2010-11-08 1:19 ` Dave Chinner
2010-11-08 5:00 ` [PATCH -v3] ext4: handle writeback of inodes which are being freed Ted Ts'o
2010-11-08 6:05 ` [PATCH -v4] " Ted Ts'o
2010-11-08 16:28 ` Nick Bowler
2010-11-08 16:54 ` Ted Ts'o
2010-11-08 6:43 ` [PATCH -v3] " Dave Chinner
2010-11-03 18:14 ` BUG in ext4 with 2.6.37-rc1 Eric Sandeen
2010-11-03 22:56 ` Dave Chinner
2010-11-05 23:09 ` Tony Vroon
2010-11-06 0:33 ` Theodore Tso
2010-11-06 0:39 ` Tony Vroon
2010-11-06 12:50 ` Ted Ts'o
2010-11-06 1:06 ` Tony Vroon
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=20101103182229.GA8766@elliptictech.com \
--to=nbowler@elliptictech.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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).