Received-SPF: pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
From:   Gabriel Krisman Bertazi <krisman@collabora.com>
To:     "Stephen E. Baker" <baker.stephen.e@gmail.com>
Cc:     linux-ext4@vger.kernel.org
Subject: Re: simplify ext4_sb_read_encoding regression
Organization: Collabora
References: <CAFDdnB38yRcZ+mQButh9UwGoh928xsZCgmjQ7r3HPEpEwdrZbg@mail.gmail.com>
Date:   Mon, 30 May 2022 10:21:54 -0400
In-Reply-To: <CAFDdnB38yRcZ+mQButh9UwGoh928xsZCgmjQ7r3HPEpEwdrZbg@mail.gmail.com>
        (Stephen E. Baker's message of "Sat, 28 May 2022 18:55:45 -0400")
Message-ID: <87sfor85j1.fsf@collabora.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Precedence: bulk

"Stephen E. Baker" <baker.stephen.e@gmail.com> writes:

> Hello,
>
> I have a Samsung Chromebook Plus (rk3399-gru-kevin) which boots linux
> off an external ssd plugged into USB. The root filesystem is ext4 with
> unicode support, case folding is enabled only on some directories in
> my home directory.
>
> Since 5.17 the system has been unbootable. I ran a git bisect and it
> pointed to aa8bf298a96acaaaa3af07d09cf7ffeb9798e48a ext4: simplify
> ext4_sb_read_encoding

Hi Stephen,

This series moved the UTF-8 data tables to a kernel module; before it,
the module had to be built-in.

Since you have your rootfs as a case-insensitive filesystem, either the
utf8data module needs to be available in the initramfs or unicode
needs to be built-in.  Are you building your own kernel?

Can you confirm that utf8data.ko exists in your initramfs, and
regenerate it if missing?  Alternatively, make sure that you have
CONFIG_UNICODE=y in your kernel configuration file.

If that doesn't work, can you provide the kernel log?  If you can't
collect the console output, a photo of the screen displaying the error
will suffice.

Thank you!

-- 
Gabriel Krisman Bertazi