From: Eric Biggers <ebiggers@kernel.org>
To: fstests@vger.kernel.org, linux-fscrypt@vger.kernel.org,
linux-ext4@vger.kernel.org
Subject: Re: [xfstests PATCH 0/2] update test_dummy_encryption testing in ext4/053
Date: Wed, 18 May 2022 10:37:47 -0700 [thread overview]
Message-ID: <YoUu60S2AjP2fEOk@sol.localdomain> (raw)
In-Reply-To: <20220518141911.zg73znk2o2krxxwk@zlang-mailbox>
On Wed, May 18, 2022 at 10:19:11PM +0800, Zorro Lang wrote:
> On Sat, Apr 30, 2022 at 10:19:26PM -0700, Eric Biggers wrote:
> > This series updates the testing of the test_dummy_encryption mount
> > option in ext4/053.
> >
> > The first patch will be needed for the test to pass if the kernel patch
> > "ext4: only allow test_dummy_encryption when supported"
> > (https://lore.kernel.org/r/20220501050857.538984-2-ebiggers@kernel.org)
> > is applied.
> >
> > The second patch starts testing a case that previously wasn't tested.
> > It reproduces a bug that was introduced in the v5.17 kernel and will
> > be fixed by the kernel patch
> > "ext4: fix up test_dummy_encryption handling for new mount API"
> > (https://lore.kernel.org/r/20220501050857.538984-6-ebiggers@kernel.org).
> >
> > This applies on top of my recent patch
> > "ext4/053: fix the rejected mount option testing"
> > (https://lore.kernel.org/r/20220430192130.131842-1-ebiggers@kernel.org).
>
> Hi Eric,
>
> Your "ext4/053: fix the rejected mount option testing" has been merged. As the
> two kernel patches haven't been merged by upstream linux, I'd like to merge
> this patchset after the kernel patches be merged. (feel free to ping me, if
> I forget this:)
Yes, I'm waiting for them to be applied.
>
> And I saw some discussion under this patchset, and no any RVB, so I'm wondering
> if you are still working/changing on it?
>
I might add a check for kernel version >= 5.19 in patch 1. Otherwise I'm not
planning any more changes.
- Eric
next prev parent reply other threads:[~2022-05-18 17:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-01 5:19 [xfstests PATCH 0/2] update test_dummy_encryption testing in ext4/053 Eric Biggers
2022-05-01 5:19 ` [xfstests PATCH 1/2] ext4/053: update the test_dummy_encryption tests Eric Biggers
2022-05-02 12:46 ` tytso
2022-05-02 17:19 ` Eric Biggers
2022-05-10 14:53 ` Theodore Ts'o
2022-05-11 8:45 ` Lukas Czerner
2022-05-01 5:19 ` [xfstests PATCH 2/2] ext4/053: test changing test_dummy_encryption on remount Eric Biggers
2022-05-18 14:19 ` [xfstests PATCH 0/2] update test_dummy_encryption testing in ext4/053 Zorro Lang
2022-05-18 17:37 ` Eric Biggers [this message]
2022-05-18 18:16 ` Zorro Lang
2022-05-18 22:01 ` Eric Biggers
2022-05-19 4:47 ` Zorro Lang
2022-05-19 8:33 ` Lukas Czerner
2022-05-19 10:40 ` Zorro Lang
2022-05-19 8:10 ` Lukas Czerner
2022-05-19 10:58 ` Lukas Czerner
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=YoUu60S2AjP2fEOk@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fscrypt@vger.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 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.