From: "Theodore Ts'o" <tytso@mit.edu>
To: "Stephen E. Baker" <baker.stephen.e@gmail.com>
Cc: adilger.kernel@dilger.ca, hch@lst.de, linux-ext4@vger.kernel.org
Subject: Re: simplify ext4_sb_read_encoding regression
Date: Mon, 30 May 2022 21:37:37 -0400 [thread overview]
Message-ID: <YpVxYchs1wScNRDw@mit.edu> (raw)
In-Reply-To: <YpVeeKRH1bycP7P1@mit.edu>
On Mon, May 30, 2022 at 08:16:56PM -0400, Theodore Ts'o wrote:
> On Mon, May 30, 2022 at 06:20:46PM -0400, Stephen E. Baker wrote:
> > The other thought I had was - this device has a strict size limit on kernels,
> > which is why I had to start building my own in the first place. Nothing over
> > 32MB can boot. However I verified my kernel was smaller than that. I
> > minimized my config even further and my Image is now 20MB uncompressed
> > which is smaller than it was before, so that's not it either.
> >
> > Here is my full config:
>
> I don't know what to tell you. I took your config, stripped out all
> of the modules, and enabled CONFIG_HYPERVISOR_GUEST,
> CONFIG_VIRTIO_MENU, and CONFIG_VIRTIO_BLK, and build a 5.16 kernel.
Sorry, this should have been 5.17 kernel.
> This worked just fine using kvm-xfstests booting into a root file
> system that had case folding enabled. (See my previous e-mail for a
> description for how to test things.)
>
> So I can't replicate your problem. Without the boot logs, I'm not
> sure what else we can do here. Maybe you can figure out a way to
> replicate the problem using kvm-xfstests? We really need a solid
> reproducer on a system where we can debug things and see the kernel
> logs.
>
> - Ted
next prev parent reply other threads:[~2022-05-31 1:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFDdnB1Rq3vNe_qt_0u+inzOuL4vrGhgbOoQZKBwfBktni=Npw@mail.gmail.com>
2022-05-29 1:24 ` simplify ext4_sb_read_encoding regression 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 [this message]
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
2022-05-28 22:55 Stephen E. Baker
2022-05-30 14:21 ` Gabriel Krisman Bertazi
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
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=YpVxYchs1wScNRDw@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=baker.stephen.e@gmail.com \
--cc=hch@lst.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).