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: Thu, 2 Jun 2022 10:47:27 -0400 [thread overview]
Message-ID: <YpjNf8WGfYh31F+2@mit.edu> (raw)
In-Reply-To: <CAFDdnB1KJVSXXzXKOc+T+g1Qewr11AS4f9tFJqSMLvfpiX-5Lg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]
On Wed, Jun 01, 2022 at 10:06:04PM -0400, Stephen E. Baker wrote:
> On Mon, May 30, 2022 at 9:37 PM Theodore Ts'o <tytso@mit.edu> wrote:
> > > 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.
> >
> Maybe a silly question, but how do I enable CONFIG_HYPERVISOR_GUEST with
> this config.
So let's make things easy. Attached please find my minimal config.
This is what I use when I normally build a test kernels, and I get it
by running "kvm-xfstests install-kconfig". I use it because it's fast
to build, since it doesn't build extraneous stuff. I've also attached
the "seb-config", which is your configuration with the minimal changes
needed so it can run under qemu. The compressed size is twice as big,
and it takes 2-3 times longer to build.
I can't reproduce the problem you are seeing using kvm-xfstests using
either kernel config building on 5.17.
- Ted
[-- Attachment #2: seb-config.gz --]
[-- Type: application/gzip, Size: 40524 bytes --]
[-- Attachment #3: minimal-config.gz --]
[-- Type: application/gzip, Size: 18741 bytes --]
next prev parent reply other threads:[~2022-06-02 14:47 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
2022-06-02 2:06 ` Stephen E. Baker
2022-06-02 14:47 ` Theodore Ts'o [this message]
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=YpjNf8WGfYh31F+2@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 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.