All of lore.kernel.org
 help / color / mirror / Atom feed
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
Date: Mon, 30 May 2022 10:21:54 -0400	[thread overview]
Message-ID: <87sfor85j1.fsf@collabora.com> (raw)
In-Reply-To: <CAFDdnB38yRcZ+mQButh9UwGoh928xsZCgmjQ7r3HPEpEwdrZbg@mail.gmail.com> (Stephen E. Baker's message of "Sat, 28 May 2022 18:55:45 -0400")

"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

  reply	other threads:[~2022-05-30 15:22 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-28 22:55 simplify ext4_sb_read_encoding regression Stephen E. Baker
2022-05-30 14:21 ` Gabriel Krisman Bertazi [this message]
2022-05-30 22:27   ` Stephen E. Baker
2022-05-31  0:56     ` Dave Chinner
2022-05-31  2:39       ` Stephen E. Baker
2022-06-02 17:47     ` Gabriel Krisman Bertazi
2022-06-05  0:11       ` Stephen E. Baker
2022-06-05  3:21         ` Stephen E. Baker
2022-06-05  6:23           ` Gabriel Krisman Bertazi
2022-06-05 13:56             ` Stephen E. Baker
     [not found] <CAFDdnB1Rq3vNe_qt_0u+inzOuL4vrGhgbOoQZKBwfBktni=Npw@mail.gmail.com>
2022-05-29  1:24 ` Theodore Ts'o
2022-05-29 12:19   ` Theodore Ts'o
2022-05-29 22:49     ` Stephen E. Baker
2022-05-30  1:49       ` Theodore Ts'o
2022-05-30 22:20         ` Stephen E. Baker
2022-05-31  0:16           ` Theodore Ts'o
2022-05-31  1:37             ` Theodore Ts'o
2022-06-02  2:06               ` Stephen E. Baker
2022-06-02 14:47                 ` Theodore Ts'o
2023-04-14 23:01                   ` William McVicker
2023-04-16  5:47                     ` Christoph Hellwig
2023-04-16  5:56                       ` Christoph Hellwig
2023-04-17  3:26                         ` Theodore Ts'o
2023-04-17 16:16                           ` Will McVicker

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=87sfor85j1.fsf@collabora.com \
    --to=krisman@collabora.com \
    --cc=baker.stephen.e@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.