[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yb6XEo/RcXEZxSai@quark.localdomain>
Date: Sat, 18 Dec 2021 20:21:06 -0600
From: Eric Biggers <ebiggers@...nel.org>
To: Theodore Ts'o <tytso@....edu>
Cc: Ext4 Developers List <linux-ext4@...r.kernel.org>,
Leah Rumancik <leah.rumancik@...il.com>
Subject: Re: [PATCH] test-appliance: add ext4/050 to encrypt.exclude
On Fri, Dec 17, 2021 at 11:08:14PM -0500, Theodore Ts'o wrote:
> The ext4/050 test can't handle encrypted directories, so skip it for
> now.
>
> Signed-off-by: Theodore Ts'o <tytso@....edu>
> ---
> .../test-appliance/files/root/fs/ext4/cfg/encrypt.exclude | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/kvm-xfstests/test-appliance/files/root/fs/ext4/cfg/encrypt.exclude b/kvm-xfstests/test-appliance/files/root/fs/ext4/cfg/encrypt.exclude
> index f3c7a959..21a8b45f 100644
> --- a/kvm-xfstests/test-appliance/files/root/fs/ext4/cfg/encrypt.exclude
> +++ b/kvm-xfstests/test-appliance/files/root/fs/ext4/cfg/encrypt.exclude
> @@ -12,6 +12,11 @@ ext4/028
> # file systems with encryption enabled can't be mounted with ext3
> ext4/044
>
> +# This test to make sure ext4 directory entries are appropriately
> +# wiped after a file is deleted, or after htree operations is
> +# incompatible with an encrypted directory.
> +ext4/048
The commit message says ext4/050, but the test added to the list is ext4/048.
Is ext4/048 the one intended?
- Eric
Powered by blists - more mailing lists