Re: CONFIG_EXT4_USE_FOR_EXT23: rootfs shows as ext2 instead of ext4

[Ric Wheeler]

On 04/13/2011 12:45 PM, John Stoffel wrote:
> > > > > > "Ted" == Ted Ts'o<tytso@xxxxxxx>  writes:
> Ted>  On Tue, Apr 12, 2011 at 01:25:08PM -0400, Mark Lord wrote:
> > > Ted et al.
> > >
> > > I've only just noticed this, so I have no idea how long it has been this way.
> > >
> > > When I build a kernel with CONFIG_EXT4_USE_FOR_EXT23=y and boot from it,
> > > the ext4 root filesystem shows up as "ext2" mode, rather than "ext4".
> > >
> > > This looks very wrong to me, and quite dangerous.
> Ted>  It's a cosemtic bug, I agree, but I'm not sure why you consider it
> Ted>  dangerous.
>
> Ted>  CONFIG_EXT4_USE_FOR_EXT23 means that ext4 registers itself as
> Ted>  ext2 and/or ext3, if ext2 and/or ext3 are not configured into the
> Ted>  kernel.  Since the kernel tries to mount the file system as ext2,
> Ted>  ext3, and then ext4, and uses whichever one works first.
>
> Should it instead be:  CONFIG_EXT4_MASQUERADE_AS_EXT23 instead, so
> it's blindingly obvious what's going on here.
>
> John

No - the idea is to have use eliminate duplicate code and still be able to run 
ext2 and ext3 in the same way.

How close we come to that goal will probably vary between ext2 and ext3 now but 
it would be great to get that done eventually.

We did discuss this at LSF last week and we had some enthusiasm for keeping ext2 
code around forever more or less as "the simple" file system template :)

Ric

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/