[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YpUWAgDJAAnbbwqs@mit.edu>
Date: Mon, 30 May 2022 15:07:46 -0400
From: "Theodore Ts'o" <tytso@....edu>
To: Eric Biggers <ebiggers@...nel.org>
Cc: fstests@...r.kernel.org, linux-ext4@...r.kernel.org,
Lukas Czerner <lczerner@...hat.com>
Subject: Re: [PATCH v2] ext4/053: update the test_dummy_encryption tests
On Mon, May 30, 2022 at 10:30:44AM -0700, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@...gle.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@...hat.com>
> Signed-off-by: Eric Biggers <ebiggers@...gle.com>
I thought we were going to put in a kernel version check in so that
this won't break on pre-5.19 kernels? The thinking was that we
wouldn't be backporting commit 5f41fdaea63d to LTS or distro kernels,
so the version number check would be reliable in this instance.
Otherwise people who are testing enterprise kernels, LTS kernels,
etc., will see this test fail.
- Ted
Powered by blists - more mailing lists