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]

Date:   Sun, 29 May 2022 21:49:58 -0400
From:   "Theodore Ts'o" <tytso@....edu>
To:     "Stephen E. Baker" <baker.stephen.e@...il.com>
Cc:     adilger.kernel@...ger.ca, hch@....de, linux-ext4@...r.kernel.org
Subject: Re: simplify ext4_sb_read_encoding regression

On Sun, May 29, 2022 at 06:49:01PM -0400, Stephen E. Baker wrote:
> On Sun, May 29, 2022 at 8:19 AM Theodore Ts'o <tytso@....edu> wrote:
> 
> I had misidentified the commit, but after being more careful with my bisect and
> kernel config I ended up in the same patch set. The actual
> first bad commit is 2b3d047870120bcd46d7cc257d19ff49328fd585
> "unicode: Add utf8-data module"

What kernel config are you using?  If you have configured
CONFIG_UNICODE_UTF8_DATA is a module, that's probably your problem.
At the point when you are mounting the root file system, the Unicode
UTF-8 module is not present unless you are using an initial ramdisk
and you have set things up to include the Unicode data module in the
initrd.  That would certainly explain why the root file system failed
to mount, and since you don't have access to the early boot output,
this wouldn't have been as obvious to you.

Try configuing CONFIG_UNICODE_UTF8_DATA=y (as opposed to =m or =n),
and hopefully that will fix things for you.

Cheers,

					- Ted