From: Eric Biggers <ebiggers@kernel.org>
To: Julian Sun <sunjunchao@bytedance.com>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-ext4@vger.kernel.org, linux-fscrypt@vger.kernel.org,
fstests@vger.kernel.org
Subject: Re: ext4/004 hangs with -o inlinecrypt,test_dummy_encryption
Date: Tue, 9 Dec 2025 13:40:50 -0800 [thread overview]
Message-ID: <20251209214050.GA7867@quark> (raw)
In-Reply-To: <dfb1479b-8aef-4f55-ba5b-4ae0595c4f99@bytedance.com>
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
prev parent reply other threads:[~2025-12-09 21:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 6:59 ext4/004 hangs with -o inlinecrypt,test_dummy_encryption Christoph Hellwig
2025-12-09 8:40 ` Julian Sun
2025-12-09 9:46 ` Julian Sun
2025-12-09 21:40 ` Eric Biggers [this message]
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=20251209214050.GA7867@quark \
--to=ebiggers@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=hch@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=sunjunchao@bytedance.com \
/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.