From: "Theodore Ts'o" <tytso@mit.edu>
To: fstests@vger.kernel.org
Cc: "Theodore Ts'o" <tytso@mit.edu>
Subject: [PATCH 6/6] ext4: create file systems with the enrypt feature if necessary
Date: Tue, 28 Jun 2022 14:25:45 -0400 [thread overview]
Message-ID: <20220628182545.1834145-7-tytso@mit.edu> (raw)
In-Reply-To: <20220628182545.1834145-1-tytso@mit.edu>
The linux kernel commit 5f41fdaea63d ("ext4: only allow
test_dummy_encryption when supported") the kernel will reject mounts
with the test_dummy_encryption option if the ext4 file system does not
have the encrypt feature enabled.
There are a handful of tests (ext4/003, ext4/035, ext4/306, and
generic/260) which will format the scratch file system using a
hard-coded set of mkfs.ext4 parameters ignoring the MKFS_OPTION that
is set by the file system test config.
For file system config that includes test_dummy_encryption in
MOUNT_OPTIONS and "-O encrypt" in MKFS_OPTIONS, we need to test for
test_dummy_encryption and force the hard-coded mkfs options to enable
the encrypt feature.
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
---
tests/ext4/003 | 6 +++++-
tests/ext4/035 | 5 ++++-
tests/ext4/306 | 3 +++
tests/generic/260 | 5 ++++-
4 files changed, 16 insertions(+), 3 deletions(-)
diff --git a/tests/ext4/003 b/tests/ext4/003
index 773bcb03..6a4518e3 100755
--- a/tests/ext4/003
+++ b/tests/ext4/003
@@ -27,7 +27,11 @@ _require_scratch
_require_scratch_ext4_feature "bigalloc"
BLOCK_SIZE=$(get_page_size)
-$MKFS_EXT4_PROG -F -b $BLOCK_SIZE -O bigalloc -C $(($BLOCK_SIZE * 16)) -g 256 $SCRATCH_DEV 512m \
+FEATURES=bigalloc
+if echo "${MOUNT_OPTIONS}" | grep -q 'test_dummy_encryption' ; then
+ FEATURES=${FEATURES},encrypt
+fi
+$MKFS_EXT4_PROG -F -b $BLOCK_SIZE -O ${FEATURES} -C $(($BLOCK_SIZE * 16)) -g 256 $SCRATCH_DEV 512m \
>> $seqres.full 2>&1
_scratch_mount
diff --git a/tests/ext4/035 b/tests/ext4/035
index 1f26e766..a1ccce45 100755
--- a/tests/ext4/035
+++ b/tests/ext4/035
@@ -25,7 +25,10 @@ _require_scratch
_exclude_scratch_mount_option dax
_require_command "$RESIZE2FS_PROG" resize2fs
-$MKFS_EXT4_PROG -F -b 1024 -E "resize=262144" $SCRATCH_DEV 32768 >> $seqres.full 2>&1
+if echo "${MOUNT_OPTIONS}" | grep -q 'test_dummy_encryption' ; then
+ ENCRYPT="-O encrypt"
+fi
+$MKFS_EXT4_PROG -F -b 1024 -E "resize=262144" $ENCRYPT $SCRATCH_DEV 32768 >> $seqres.full 2>&1
if [ $? -ne 0 ]; then
_notrun "Can't make file system with a block size of 1024"
fi
diff --git a/tests/ext4/306 b/tests/ext4/306
index 2ff88537..a6b7eab5 100755
--- a/tests/ext4/306
+++ b/tests/ext4/306
@@ -33,6 +33,9 @@ features="^extents"
if grep -q 64bit /etc/mke2fs.conf ; then
features="^extents,^64bit"
fi
+if echo "${MOUNT_OPTIONS}" | grep -q 'test_dummy_encryption' ; then
+ features=${features},encrypt
+fi
blksz=$(get_page_size)
diff --git a/tests/generic/260 b/tests/generic/260
index b4d72e0f..e86afe9c 100755
--- a/tests/generic/260
+++ b/tests/generic/260
@@ -120,7 +120,10 @@ case $FSTYP in
bsize=4096
start=$(_math "$base*$agsize*$bsize")
len=$start
- export MKFS_OPTIONS="-F -b $bsize -g $agsize"
+ if echo "${MOUNT_OPTIONS}" | grep -q 'test_dummy_encryption' ; then
+ ENCRYPT="-O encrypt"
+ fi
+ export MKFS_OPTIONS="-F -b $bsize -g $agsize $ENCRYPT"
;;
xfs)
agsize=65538
--
2.31.0
next prev parent reply other threads:[~2022-06-28 18:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 18:25 [PATCH -v2 0/6] Miscellaneous ext4 test fix ups Theodore Ts'o
2022-06-28 18:25 ` [PATCH 1/6] ext4/050: support indirect as well as extent mapped journals Theodore Ts'o
2022-06-28 18:25 ` [PATCH 2/6] ext4/044: skip test if the file system does not have a journal Theodore Ts'o
2022-06-28 18:25 ` [PATCH 3/6] ext4/045: _require_dumpe2fs doesn't take any arguments so remove them Theodore Ts'o
2022-06-28 18:25 ` [PATCH 4/6] ext4/054: skip test if the dax mount option is enabled Theodore Ts'o
2022-06-28 18:25 ` [PATCH 5/6] ext4/055: skip test if dax mount option is used Theodore Ts'o
2022-06-28 18:25 ` Theodore Ts'o [this message]
2022-06-29 5:16 ` [PATCH 6/6] ext4: create file systems with the enrypt feature if necessary Eric Biggers
2022-06-29 12:28 ` Theodore Ts'o
2022-06-29 8:58 ` 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=20220628182545.1834145-7-tytso@mit.edu \
--to=tytso@mit.edu \
--cc=fstests@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox