From: Eric Biggers <ebiggers@kernel.org>
To: fstests@vger.kernel.org
Cc: linux-f2fs-devel@lists.sourceforge.net,
linux-fscrypt@vger.kernel.org,
Gabriel Krisman Bertazi <krisman@collabora.com>,
Daniel Rosenberg <drosen@google.com>
Subject: [xfstests PATCH] generic/556: add test case for top-level dir rename
Date: Sat, 14 May 2022 11:01:46 -0700 [thread overview]
Message-ID: <20220514180146.44775-1-ebiggers@kernel.org> (raw)
From: Eric Biggers <ebiggers@google.com>
Test renaming a casefolded directory located in the top-level directory,
while the cache is cold. When $MOUNT_OPTIONS contains
test_dummy_encryption, this detects an f2fs bug.
Signed-off-by: Eric Biggers <ebiggers@google.com>
---
tests/generic/556 | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/tests/generic/556 b/tests/generic/556
index 7ef2f6f4..8abb65e8 100755
--- a/tests/generic/556
+++ b/tests/generic/556
@@ -348,6 +348,21 @@ test_file_rename()
echo "Name shouldn't change."
}
+test_toplevel_dir_rename()
+{
+ local dir=${SCRATCH_MNT}/dir_rename
+
+ # With the cache cold, rename a casefolded directory located in the
+ # top-level directory. If $MOUNT_OPTIONS contains
+ # test_dummy_encryption, this detects the bug that was fixed by
+ # 'f2fs: don't use casefolded comparison for "." and ".."'.
+ mkdir ${dir}
+ _casefold_set_attr ${dir}
+ sync
+ echo 2 > /proc/sys/vm/drop_caches
+ mv ${dir} ${dir}.new
+}
+
# Test openfd with casefold.
# 1. Delete a file after gettings its fd.
# 2. Then create new dir with same name
@@ -486,6 +501,7 @@ test_dir_name_preserve
test_name_reuse
test_create_with_same_name
test_file_rename
+test_toplevel_dir_rename
test_casefold_openfd
test_casefold_openfd2
test_hard_link_lookups
base-commit: bb04d577435d04ce3aa160f0563d1d35d4860d54
--
2.36.1
next reply other threads:[~2022-05-14 18:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-14 18:01 Eric Biggers [this message]
2022-05-20 17:21 ` [xfstests PATCH] generic/556: add test case for top-level dir rename Gabriel Krisman Bertazi
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=20220514180146.44775-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=drosen@google.com \
--cc=fstests@vger.kernel.org \
--cc=krisman@collabora.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox