linux-ext4 - Re: EXT4-fs (mmcblk0p1): couldn't mount as ext3 due to feature incompatibilities

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <e7bcce88-992b-92fb-f9e9-1df161af5781@redhat.com>
Date:   Fri, 2 Mar 2018 10:13:54 -0600
From:   Eric Sandeen <sandeen@...hat.com>
To:     Joakim Tjernlund <Joakim.Tjernlund@...inera.com>,
        "lczerner@...hat.com" <lczerner@...hat.com>
Cc:     "linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: Re: EXT4-fs (mmcblk0p1): couldn't mount as ext3 due to feature
 incompatibilities

On 3/2/18 9:55 AM, Joakim Tjernlund wrote:
> On Fri, 2018-03-02 at 16:43 +0100, Joakim Tjernlund wrote:
>> On Fri, 2018-03-02 at 09:34 -0600, Eric Sandeen wrote:
>>> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
>>>
>>>
>>> On 3/2/18 9:20 AM, Joakim Tjernlund wrote:
>>>> On Fri, 2018-03-02 at 08:42 -0600, Eric Sandeen wrote:
>>>
>>> ...
>>>
>>>>> ext3 is always going to print a message if mount fails for this reason; it
>>>>> has no idea that ext4 will be tried next, all it knows is that it was told
>>>>> to mount, and it can't.
>>>>
>>>> But I don't hav ext3, only ext4 in kernel:
>>>> # CONFIG_EXT2_FS is not set
>>>> # CONFIG_EXT3_FS is not set
>>>> CONFIG_EXT4_FS=y
>>>>
>>>> ext4 know's ext3 and complains as is today. In this config one should not have to see
>>>> this error.
>>>
>>> ext4.ko was told to mount your disk /as an ext3 filesystem/, and ext4.ko issued an
>>> error saying that was not possible.  It is doing the right thing.
>>
>> hmm, so you think there is a bug in my system ?
>> It works for you(no error msg) if you specify auto type in fstab?
> 
> It seems to that ext4/3/2 is one of few(only?) FS:es that
> report an error during mount -t auto probing and that is why I see this.

I had forgotten that there is a flag during autprobing, SB_SILENT, thanks
for the reminder.

Maybe ext4_fill_super needs to honor that to a greater degree, I'll fling
a patch.

-Eric

>  Jocke
>