[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251209214050.GA7867@quark>
Date: Tue, 9 Dec 2025 13:40:50 -0800
From: Eric Biggers <ebiggers@...nel.org>
To: Julian Sun <sunjunchao@...edance.com>
Cc: Christoph Hellwig <hch@...radead.org>, linux-ext4@...r.kernel.org,
linux-fscrypt@...r.kernel.org, fstests@...r.kernel.org
Subject: Re: ext4/004 hangs with -o inlinecrypt,test_dummy_encryption
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@...edance.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
Powered by blists - more mailing lists