From: Jan Kara <jack@suse.cz>
To: Carlos Maiolino <cmaiolino@redhat.com>
Cc: Jan Kara <jack@suse.cz>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: check incompatible mount options when mounting ext2/3 [V2]
Date: Wed, 23 Jan 2013 14:00:37 +0100 [thread overview]
Message-ID: <20130123130037.GA23741@quack.suse.cz> (raw)
In-Reply-To: <20130123122249.GA1423@localhost.localdomain>
On Wed 23-01-13 07:22:49, Carlos Maiolino wrote:
> On Wed, Jan 23, 2013 at 11:39:17AM +0100, Jan Kara wrote:
> > On Tue 22-01-13 11:07:58, Carlos Maiolino wrote:
> > > This checks for incompatible mounting options when using ext4 module to mount
> > > ext3 or ext2 filesystems.
> > >
> > > Sets two new flags to group ext4 mount options that are incompatible with ext2
> > > and ext3, and then add two functions -- check_ext2/3_incompat_mount() -- to
> > > check and warn/fail mount, if any of these options are being used.
> > >
> > > I believe, some options like those expecting an argument needs to be checked
> > > during parsing time.
> > >
> > > barrier mount, although it has a flag, when mounting an ext2fs, where
> > > barriers are not supported (afaik), should also be checked during parse
> > > time, otherwise the BARRIER mount flag will be set.
> > >
> > > I didn't add all mount options I believe to need to raise a warning, just
> > > those with a flag set on superblock, another flags should be added after a
> > > discussion to reach a concensus of all ext2/3 options that should be rejected by
> > > ext4 mount.
> > Thinking about it a bit more I'm not sure if restricting mount options is
> > the right thing to start with. IMHO what we should restrict is mounting
> > filesystem with certain *features* as ext3/ext2. So e.g. filesystem with
> > EXT4_FEATURE_INCOMPAT_EXTENTS cannot be mounted as ext2 or ext3. Similarly
> > as currently we forbid mounting ext3 filesystem with
> > EXT3_FEATURE_INCOMPAT_RECOVER as ext2... This should avoid the confusion
> > which could arise when someone reports problems with "ext3" filesystem but
> > actually has some of the ext4 features enabled.
> >
> This is interesting, but I wonder if not restricting mount options, but
> features, would open a 'window' to let users change their filesystem on-disk
> format without know what they are doing, but I might be wrong.
If there are mount options that enable features, then these should be
disallowed for ext2/ext3 mounts. But I think we already got rid of these
traps on users...
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2013-01-23 13:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-01 19:32 [PATCH] ext4: check incompatible mount options when mounting ext2/3 Carlos Maiolino
2012-11-08 17:02 ` Theodore Ts'o
2012-11-11 22:16 ` Eric Sandeen
2012-11-15 20:03 ` Ric Wheeler
2012-11-23 16:20 ` Carlos Maiolino
2013-01-22 16:07 ` [PATCH] ext4: check incompatible mount options when mounting ext2/3 [V2] Carlos Maiolino
2013-01-23 10:39 ` Jan Kara
2013-01-23 12:22 ` Carlos Maiolino
2013-01-23 13:00 ` Jan Kara [this message]
2013-10-31 14:00 ` Carlos Maiolino
2013-11-19 18:39 ` Carlos Maiolino
2013-11-22 1:43 ` Carlos Maiolino
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=20130123130037.GA23741@quack.suse.cz \
--to=jack@suse.cz \
--cc=cmaiolino@redhat.com \
--cc=linux-ext4@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 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).