From: Dave Chinner <david@fromorbit.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Jan Kara <jack@suse.cz>, Jan Kara <jack@suse.com>,
linux-ext4 <linux-ext4@vger.kernel.org>,
Theodore Ts'o <tytso@mit.edu>
Subject: Re: [PATCH] ext2: don't mount filesystems with compat features we know only ext4 supports
Date: Thu, 1 Oct 2015 12:00:42 +1000 [thread overview]
Message-ID: <20151001020041.GF3902@dastard> (raw)
In-Reply-To: <20150930163635.GK10390@birch.djwong.org>
On Wed, Sep 30, 2015 at 09:36:35AM -0700, Darrick J. Wong wrote:
> On Wed, Sep 30, 2015 at 10:41:26AM +0200, Jan Kara wrote:
> > On Mon 28-09-15 15:36:26, Darrick J. Wong wrote:
> > > The ext2 mount code never checks the compat features against the ones
> > > it knows about. This is correct behavior since compat features are
> > > supposed to be rw-compatible with old drivers; however, for certain
> > > configurations (journalled rootfs) we probably want the ext4 driver
> > > to load, not ext2.
> > >
> > > Reported-by: Dave Chinner <david@fromorbit.com>
> > > Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> >
> > Isn't this a bit too harsh? I agree we should at least warn (and that's
> > probably regardless of EXT4 config option) but just refusing mount looks
> > too much to me...
>
> I admit that refusing the mount might be a bit much; the goal here was
> merely to make it so that if the FS has a journal and ext4 was turned on,
> hopefully ext2 rejects the mount and ext4 will probe it next.
IMO it's worse to have the ext2 module is *incorrectly*
mounting ext3 filesystems and users silently losing the protection
of journalling. Perhaps we should simply make ext4 probe before
ext2 probes anything. Anything that is not explicitly an ext4 or
ext3 filesystem can then be left to the ext2 module (if EXT4 is not
configured to also handle ext2).
But, really, I don't care enough about this to spend any more time
on it - my systems are working again so it's up the the EXT
maintainers to decide what to do with the problem...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2015-10-01 2:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-28 22:36 [PATCH] ext2: don't mount filesystems with compat features we know only ext4 supports Darrick J. Wong
2015-09-30 8:41 ` Jan Kara
2015-09-30 16:36 ` Darrick J. Wong
2015-10-01 2:00 ` Dave Chinner [this message]
2015-10-07 13:29 ` Jan Kara
2015-10-08 18:08 ` Darrick J. Wong
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=20151001020041.GF3902@dastard \
--to=david@fromorbit.com \
--cc=darrick.wong@oracle.com \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=linux-ext4@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).