From: Theodore Tso <tytso@mit.edu>
To: Andrew Price <andy@andrewprice.me.uk>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: BUG: using rootfstype=ext4 causes oops
Date: Thu, 16 Apr 2009 12:55:34 -0400 [thread overview]
Message-ID: <20090416165534.GO21586@mit.edu> (raw)
In-Reply-To: <20090416163835.GB433@sucs.org>
On Thu, Apr 16, 2009 at 05:38:36PM +0100, Andrew Price wrote:
> On Thu, Apr 16, 2009 at 10:53:57AM -0400, Theodore Tso wrote:
> > OK, can you confirm that you tried using ext4 with either 2.6.29 or
> > 2.6.28, and it was working previously? That would make it a
> > regression which Rafael would track.
>
> I've tested this with a local GFS2 mount (which uses barriers too) and
> the same bug occurs. Apologies for making it seem like an ext4 bug. I'm
> currently waiting for a kernel to build with Bartlomiej's patch so we'll
> see how that goes.
No, no, that's fine. That sort of thing we get all the time; it's
part of trying to find the root cause of the bug. What I was more
interested in was trying to figure out when (at which kernel version)
the bug had introduced; if it's a recent regression then Rafael would
be interested in tracking it as such.
> Further up in that file in the last paragraph of the 'Quick usage
> instructions' it says:
>
> [...]
> '-o barriers=[0|1]' mount option for both ext3 and ext4 filesystems
> [...]
>
OK, got it. Thanks. I'll queue up a patch to fix that up.
- Ted
prev parent reply other threads:[~2009-04-16 16:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 20:59 BUG: using rootfstype=ext4 causes oops Andrew Price
2009-04-16 4:19 ` Theodore Tso
2009-04-16 10:47 ` Andrew Price
2009-04-16 14:53 ` Theodore Tso
2009-04-16 16:02 ` Bartlomiej Zolnierkiewicz
2009-04-16 17:05 ` Andrew Price
2009-04-16 19:22 ` Bartlomiej Zolnierkiewicz
2009-04-16 16:38 ` Andrew Price
2009-04-16 16:55 ` Theodore Tso [this message]
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=20090416165534.GO21586@mit.edu \
--to=tytso@mit.edu \
--cc=andy@andrewprice.me.uk \
--cc=bzolnier@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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