From: Ross Lagerwall <rosslagerwall@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: another ext3 kernel BUG
Date: Fri, 17 Jun 2011 07:23:13 +0200 [thread overview]
Message-ID: <1308288193.17587.3.camel@hobo> (raw)
> See here for a patch:
> https://lkml.org/lkml/2011/6/15/341
>
> Does that help?
I came across this bug while running ./configure on Octave 3.4.1.
The patch does appear to fix the problem although I can't say whether
what it is doing is correct or not.
There is also a bug report at:
https://bugzilla.kernel.org/show_bug.cgi?id=37602
Cheers
Ross
next reply other threads:[~2011-06-17 5:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 5:23 Ross Lagerwall [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-11 2:17 ext3 and btrfs various Oops and kernel BUGs Norbert Preining
2011-06-14 1:19 ` another ext3 kernel BUG Norbert Preining
2011-06-14 2:19 ` Eric Sandeen
2011-06-14 2:43 ` Norbert Preining
2011-06-14 3:21 ` Dave Jones
2011-06-14 3:32 ` Eric Sandeen
2011-06-14 4:03 ` Norbert Preining
2011-06-15 1:23 ` Norbert Preining
2011-06-15 1:23 ` Norbert Preining
2011-06-15 8:09 ` Török Edwin
2011-06-16 5:51 ` Norbert Preining
2011-06-16 7:02 ` Török Edwin
2011-06-16 8:28 ` Norbert Preining
2011-06-16 8:28 ` Norbert Preining
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=1308288193.17587.3.camel@hobo \
--to=rosslagerwall@gmail.com \
--cc=linux-kernel@vger.kernel.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 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.