From: Eric Biggers <ebiggers@kernel.org>
To: fstests@vger.kernel.org
Cc: linux-fscrypt@vger.kernel.org, linux-ext4@vger.kernel.org,
Lukas Czerner <lczerner@redhat.com>
Subject: [xfstests PATCH 2/2] ext4/053: test changing test_dummy_encryption on remount
Date: Sat, 30 Apr 2022 22:19:28 -0700 [thread overview]
Message-ID: <20220501051928.540278-3-ebiggers@kernel.org> (raw)
In-Reply-To: <20220501051928.540278-1-ebiggers@kernel.org>
From: Eric Biggers <ebiggers@google.com>
The test_dummy_encryption mount option isn't supposed to be settable or
changeable via a remount, so add test cases for this.
Signed-off-by: Eric Biggers <ebiggers@google.com>
---
tests/ext4/053 | 3 +++
1 file changed, 3 insertions(+)
diff --git a/tests/ext4/053 b/tests/ext4/053
index 84f3eab9..3d530953 100755
--- a/tests/ext4/053
+++ b/tests/ext4/053
@@ -686,6 +686,9 @@ for fstype in ext2 ext3 ext4; do
mnt test_dummy_encryption=v2
not_mnt test_dummy_encryption=bad
not_mnt test_dummy_encryption=
+ # Can't be set or changed on remount.
+ mnt_then_not_remount defaults test_dummy_encryption
+ mnt_then_not_remount test_dummy_encryption=v1 test_dummy_encryption=v2
do_mkfs -O ^encrypt $SCRATCH_DEV ${SIZE}k
fi
not_mnt test_dummy_encryption
--
2.36.0
next prev parent reply other threads:[~2022-05-01 5:21 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 ` Eric Biggers [this message]
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
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=20220501051928.540278-3-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=lczerner@redhat.com \
--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.