Re: [PATCH v2] Add EXT4_STATE_MAY_INLINE_DATA check in ext4_readdir

On Sun, Aug 16, 2026 at 11:12:33PM -0400, Theodore Tso wrote:
> Since you are making changes to inline_data feature, you'd use it
> soemthing like this:
> 
> % cd /usr/src/linux  # replace with your kernel sources
> % install-kconfig
> % kbuild
> % kvm-xfstests -c ext4/inline -g auto

Thank you very much for your detailed guidance on the testing process.
I will fix the issues reported by Sashiko and Syzbot.

> 
> You can also add some options to install-kconfig to enable extra
> debugging, of which the most interesting are --kasan and --lockdep.  I
> would recommend doing your initial testing using just the plain
> install-kconfig, and then once you are getting clean run, do separate
> runs with the Kernel Address Sanitizer and the runtime locking
> correctness validator.

I'll run the tests following your recommended sequence.

> 
> The way I do my testing using gce-xfstests is to use a command like
> this: "gce-xfstests ltm -c ext4/all -g auto" which will launch 12
> VM's, for a variety of ext4 test scenarios (e.g., with bigalloc, fast
> commit, 1k block sizes, etc.)  You can of course try running
> "kvm-xfstests -c ext4/all -g auto" but this will likely take around
> 24-36 hours depending on how fast your local storage test devices.
> (Using gce-xfstest's lightweight test manager takes around 2 hours of
> wall clock time, since the test VM's run in parallel.)

Regarding gce-xfstests, I don't have Google Cloud access at the moment,
but I'll also try running "kvm-xfstests -c ext4/all -g auto" locally to
cover more scenarios.

I'll send the v3 patch along with the test results once everything is
ready.