linux-ext4 - Re: simplify ext4_sb_read

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: <CAFDdnB0uH_KqpN12pE2pyfb-vh_6Uab8Xdcb=NzQQy8ATEL+gA@mail.gmail.com>
Date:   Sat, 4 Jun 2022 23:21:46 -0400
From:   "Stephen E. Baker" <baker.stephen.e@...il.com>
To:     Gabriel Krisman Bertazi <krisman@...labora.com>,
        amstan@...omium.org, "Theodore Ts'o" <tytso@....edu>
Cc:     linux-ext4@...r.kernel.org
Subject: Re: simplify ext4_sb_read_encoding regression

On Sat, Jun 4, 2022 at 8:11 PM Stephen E. Baker
<baker.stephen.e@...il.com> wrote:
>
> I reached out on the archlinuxarm IRC room and amstan offered the use
> of his device.
>
> When he boots my image he sees:
> "EXT4-fs (sda2): can't mount with superblock charset: utf8-12.1.0 not
> supported by the kernel. flags: 0x0."

At amstan's request I created a new root filesystem without casefold,
and created a loop device with casefold enabled. I am able to boot
with that filesystem.

zgrep UNICODE /proc/config
CONFIG_UNICODE=y
CONFIG_UNICODE_UTF8_DATA=y
CONFIG_UNICODE_NORMALIZATION_SELFTEST=m

mount /dev/loop0p1 /mnt
[ 679.358591] EXT-fs (loop0p1): can't mount with superblock charset:
utf8-12.1.0 not supported by the kernel. flags: 0x0
mount: /mnt: wrong fs type, bad option, bad superblock on
/dev/loop0p1, missing codepage or helper program, or other error.

So it seems I can produce the same error after boot that we saw in
early boot, which makes debugging much easier.

Given that is there anything I should be trying / looking for?