From: Eric Biggers <ebiggers@kernel.org>
To: Zorro Lang <zlang@kernel.org>
Cc: fstests@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [PATCH v2] ext4/053: update the test_dummy_encryption tests
Date: Thu, 2 Jun 2022 22:48:28 -0700 [thread overview]
Message-ID: <YpmgrJHnrMR8BcOG@sol.localdomain> (raw)
In-Reply-To: <20220603053143.ud42tcsxrdkr3mj2@zlang-mailbox>
On Fri, Jun 03, 2022 at 01:31:43PM +0800, Zorro Lang wrote:
> On Mon, May 30, 2022 at 10:30:44AM -0700, Eric Biggers wrote:
> > From: Eric Biggers <ebiggers@google.com>
> >
> > Kernel commit 5f41fdaea63d ("ext4: only allow test_dummy_encryption when
> > supported") tightened the requirements on when the test_dummy_encryption
> > mount option is accepted. Update ext4/053 accordingly.
> >
> > Move the test cases to later in the file to group them with the other
> > test cases that use do_mkfs to add custom mkfs options instead of using
> > the "default" filesystem that the test creates at the beginning.
> >
> > Reviewed-by: Lukas Czerner <lczerner@redhat.com>
> > Signed-off-by: Eric Biggers <ebiggers@google.com>
> > ---
> >
> > v2: mention the commit ID now that it is merged, and add a Reviewed-by
>
> Hi Eric,
>
> If I don't remember wrong, it was a patchset with 2 patches. Now you only
> send this patch out, do you hope to merge this one only, or merge both?
>
> Thanks,
> Zorro
>
Just this one for now. The second patch would add a test for the bug fix
https://lore.kernel.org/linux-ext4/20220526040412.173025-1-ebiggers@kernel.org,
but that wasn't applied for 5.19 due to a cross-tree dependency. I'll be
resending that test patch later. One step at a time...
- Eric
next prev parent reply other threads:[~2022-06-03 5:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 17:30 [PATCH v2] ext4/053: update the test_dummy_encryption tests Eric Biggers
2022-05-30 19:07 ` Theodore Ts'o
2022-05-30 19:47 ` Eric Biggers
2022-06-03 5:31 ` Zorro Lang
2022-06-03 5:48 ` Eric Biggers [this message]
2022-06-03 7:40 ` Zorro Lang
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=YpmgrJHnrMR8BcOG@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=zlang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox