All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Richard Yao <ryao@gentoo.org>, Jan Kara <jack@suse.cz>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Raymond Jennings <shentino@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"Theodore Ts'o" <tytso@mit.edu>, Albino B Neto <bino@riseup.net>
Subject: Re: [GIT PULL] Ext3 removal, quota & udf fixes
Date: Thu, 3 Sep 2015 13:36:45 -0500	[thread overview]
Message-ID: <55E8933D.6010906@redhat.com> (raw)
In-Reply-To: <20150903182225.GA7732@woodpecker.gentoo.org>

On 9/3/15 1:22 PM, Richard Yao wrote:
> What happens with this patch if /dev/$DEVICE is ext4 formatted and someone runs
> `mount -t ext3 /dev/$DEVICE $MNT`?
> 
> This should fail with the ext3 driver, but it looks like it will work fine with
> CONFIG_EXT4_USE_FOR_EXT23 because ext3_fs_type maps to ext4_mount.

Did you test it?

# truncate --size=1g fsfile
# mkfs.ext4 fsfile
# mount -o loop -t ext3 fsfile
mount: wrong fs type, <snip>
# dmesg | tail
# EXT4-fs: (loop0): couldn't mount as ext3 due to feature incompatibilities

> My system is
> not built with CONFIG_EXT4_USE_FOR_EXT23 (long story short: it uses a RHEL6
> derived config on Linux 4.1) and I do not have time to rebuild it to verify my
> suspicion, but I imagine there are others on the list that could trivially check
> this.

Well by all means, let me do that for you.  :)

> Also, new kernels are typically drop-in replacements on older userlands. An edge
> case that no one appears to have mentioned is the possibility of using a newer
> kernel on an older system where the initramfs generator might only include ext3,
> which this would break. It might not be terrible to write a small dummy ext3
> module whose only purpose is to depend on ext4 and load it into the kernel on
> those systems. That way initramfs software that properly grabs module
> dependencies will include the ext4 module and `modprobe ext3` will do what it
> always did in terms of making ext3 file systems mountable. I suppose that we
> could use aliases, but given that there is a compatibility shim for CONFIG_EXT3
> to avoid surprises, a dummy module seems reasonable.

I'm not wise in the ways of initramfs generation, so I'll defer on this one.

-Eric

> These are the only two things that I see preventing ext4 from being a drop-in
> replacement for ext3.
> 
> That said, my only connection with ext3/ext4 is that I am one of the genkernel
> developers (Gentoo's  Linux initramfs/kernel genreation framework/scripts), so
> my opinion might not matter much here, but I am also in favor of killing ext3 in
> favor of CONFIG_EXT4_USE_FOR_EXT23.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

  reply	other threads:[~2015-09-03 18:36 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31  6:19 [GIT PULL] Ext3 removal, quota & udf fixes Jan Kara
2015-08-31 21:37 ` Linus Torvalds
2015-08-31 22:31   ` Raymond Jennings
2015-08-31 22:39     ` Linus Torvalds
2015-08-31 23:03       ` Raymond Jennings
2015-09-01  2:53       ` Theodore Ts'o
2015-09-01 12:52       ` Eric Sandeen
2015-09-01 15:17         ` Jeff Mahoney
2015-09-01  0:24     ` Raymond Jennings
2015-09-01  6:44     ` Christoph Hellwig
2015-09-01 10:29     ` Albino B Neto
2015-09-01 19:39       ` Austin S Hemmelgarn
2015-09-01 23:58         ` Theodore Ts'o
2015-09-02 16:58           ` Austin S Hemmelgarn
2015-09-02  3:30         ` Albino B Neto
2015-09-02  5:46           ` Raymond Jennings
2015-09-02 13:28             ` Austin S Hemmelgarn
2015-09-02 11:58         ` Chuck Ebbert
2015-09-02 13:33           ` Austin S Hemmelgarn
2015-09-01  0:23   ` Andreas Dilger
2015-09-02 16:52   ` Mel Gorman
2015-09-02 18:45     ` Darrick J. Wong
2015-09-02 23:47       ` Linus Torvalds
2015-09-03 11:28         ` Albino B Neto
2015-09-03 21:49           ` Darrick J. Wong
2015-09-15  5:31         ` Jan Kara
2015-09-03 18:22 ` Richard Yao
2015-09-03 18:36   ` Eric Sandeen [this message]
2015-09-03 19:13     ` Richard Yao
2015-09-03 18:36   ` Darrick J. Wong
2015-09-03 19:16     ` Richard Yao
2015-09-03 19:36       ` Darrick J. Wong
2015-09-03 22:26         ` Richard Yao

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=55E8933D.6010906@redhat.com \
    --to=sandeen@redhat.com \
    --cc=bino@riseup.net \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ryao@gentoo.org \
    --cc=shentino@gmail.com \
    --cc=torvalds@linux-foundation.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 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.