linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lord <kernel@teksavvy.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>,
	linux-ext4@vger.kernel.org, "Theodore Ts'o" <tytso@mit.edu>
Subject: CONFIG_EXT4_USE_FOR_EXT23:  rootfs shows as ext2 instead of ext4
Date: Tue, 12 Apr 2011 13:25:08 -0400	[thread overview]
Message-ID: <4DA48AF4.5080803@teksavvy.com> (raw)

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.

Eg.  I test it by building my own kernel (2.6.38.2), with ext4 built-in,
no initramfs required, and boot:

    root=/dev/sda1 init=/bin/bash
    ...
    $ mount /proc
    $ cat /proc/mounts
    /dev/root / ext2 ro,relatime,barrier=1,data=ordered 0 0

So.. it shows "ext2" instead of "ext4".  That really looks like a bug.
Especially since it appears to be using journaling regardless.

Building the kernel without CONFIG_EXT4_USE_FOR_EXT23
results in a proper "ext4" mount entry in /proc/mounts.


             reply	other threads:[~2011-04-12 17:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-12 17:25 Mark Lord [this message]
2011-04-13  0:49 ` CONFIG_EXT4_USE_FOR_EXT23: rootfs shows as ext2 instead of ext4 Ted Ts'o
2011-04-13 14:05   ` Mark Lord
2011-04-13 14:10   ` Mark Lord
2011-04-13 21:00     ` Theodore Tso
2011-04-13 22:30       ` Joel Becker
2011-04-14 15:41         ` [PATCH] ext4: register ext2 and ext3 alias after ext4 Milton Miller
2011-04-15  1:07           ` Mark Lord
2011-04-17  2:01           ` Ted Ts'o
2011-04-14  1:34       ` CONFIG_EXT4_USE_FOR_EXT23: rootfs shows as ext2 instead of ext4 Mark Lord
2011-04-14 12:47         ` Theodore Tso
2011-04-13 16:45   ` John Stoffel
2011-04-13 18:17     ` Ric Wheeler

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=4DA48AF4.5080803@teksavvy.com \
    --to=kernel@teksavvy.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@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).