All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: Theodore Tso <tytso@mit.edu>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-ext4@vger.kernel.org,
	Linux Kernel Development <linux-kernel@vger.kernel.org>,
	Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: Problem mounting ext2 using ext3?
Date: Tue, 6 May 2008 11:50:26 +0200	[thread overview]
Message-ID: <20080506095026.GA1409@duck.suse.cz> (raw)
In-Reply-To: <19f34abd0805060026m138bf3dfo87dbf303362d69ca@mail.gmail.com>

On Tue 06-05-08 09:26:30, Vegard Nossum wrote:
> Hi,
> 
> On Tue, May 6, 2008 at 12:26 AM, Theodore Tso <tytso@mit.edu> wrote:
> > On Mon, May 05, 2008 at 11:11:46PM +0200, Geert Uytterhoeven wrote:
> >  > when mounting the root file system, which is ext2 (has_journal is not set).
> >  > Apparently it crashes in ext3_sync_fs because EXT3_SB(sb)->s_journal is NULL.
> >  >
> >  > At first I thought it was an issue with the byteswapped IDE bus on Atari (a
> >  > new and different solution to handle this just went into mainline), but if I
> >  > disable CONFIG_EXT3 support, it boots up fine.
> >  >
> >  > Is this a known problem?
> >
> >  I can confirm this as a regression.  You don't even need to mount it
> >  as a root filesystem, or do this on an 68k system.  On my x86 system,
> >  using a kernel based off of git commit: afa26be8 (6 commits after
> >  2.6.26-rc1), mounting an ext3 filesystem, you can cause an oops by
> >  taking an ext2 filesystem and forcing a mount as ext3, "mount -t ext3
> >  /dev/closure/textext2fs /mnt").  (see below for my oops).  This does
> >  not occur with a kernel based off of 2.6.25, so it's a definite
> >  regression.
> 
> Hi,
> 
> I posted a very similar problem a couple of days ago:
> http://www.nabble.com/BUG-in-ext3_sync_fs-td16999997.html
> 
> to which I got zero replies. Can I close this in my internal bugzilla
> as dup/"not my fault"? The stacktrace looks very similar. This was
> also ext2 fs mounted (apparently) by ext3 code.
  Yes, this looks like the same problem. I'll take care of that.

								Honza
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

  reply	other threads:[~2008-05-06  9:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-05 21:11 Problem mounting ext2 using ext3? Geert Uytterhoeven
2008-05-05 22:26 ` Theodore Tso
2008-05-06  7:11   ` Geert Uytterhoeven
2008-05-06  7:26   ` Vegard Nossum
2008-05-06  7:26     ` Vegard Nossum
2008-05-06  9:50     ` Jan Kara [this message]
2008-05-06 12:05     ` Theodore Tso
2008-05-06 10:02   ` Jan Kara
2008-05-06 10:02     ` Jan Kara
2008-05-06 11:20     ` Geert Uytterhoeven
2008-05-06 19:05     ` Geert Uytterhoeven

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=20080506095026.GA1409@duck.suse.cz \
    --to=jack@suse.cz \
    --cc=geert@linux-m68k.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=vegard.nossum@gmail.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.