* Re: ext4/004 hangs with -o inlinecrypt,test_dummy_encryption
[not found] ` <dfb1479b-8aef-4f55-ba5b-4ae0595c4f99@bytedance.com>
@ 2025-12-09 21:40 ` Eric Biggers
0 siblings, 0 replies; only message in thread
From: Eric Biggers @ 2025-12-09 21:40 UTC (permalink / raw)
To: Julian Sun; +Cc: Christoph Hellwig, linux-ext4, linux-fscrypt, fstests
On Tue, Dec 09, 2025 at 05:46:22PM +0800, Julian Sun wrote:
> On 12/9/25 4:40 PM, Julian Sun wrote:
> >
> > I can reproduce this issue locally with both v6.18 and v6.0. The problem
> > disappears after removing test_dummy_encryption, and it still reproduces
> > when test_dummy_encryption is set alone in MOUNT_OPTIONS. Therefore, I
> > believe the issue lies in test_dummy_encryption — it is an
> > implementation of fscrypt.
> >
> > CC: linux-fscrypt
> >
> > Thanks,
>
> cc linux-fscrypt
>
> --
> Julian Sun <sunjunchao@bytedance.com>
>
It seems to be a known failure. ext4/004, along with various other
tests, is excluded by
https://github.com/tytso/xfstests-bld/blob/master/test-appliance/files/root/fs/ext4/cfg/encrypt.exclude
as follows:
ext4/004 // dump/restore doesn't handle quotas
I'm not sure why the comment mentions quotas. It probably should say
"encryption", not "quotas".
Either way, the exclusion logic in xfstests-bld really should be
incorporated directly into xfstests, e.g. by using
_exclude_test_mount_option "test_dummy_encryption".
This seems to be a wider issue. Effectively, ext4's exclusion lists for
xfstests are being maintained outside of xfstests itself.
- Eric
^ permalink raw reply [flat|nested] only message in thread