From: Kent Overstreet <kent.overstreet@gmail.com>
To: fstests@vger.kernel.org
Subject: [PATCH] generic/544: Fix inode number ordering code
Date: Sat, 13 Nov 2021 16:00:03 -0500 [thread overview]
Message-ID: <YZAnUyyKgaddwOQH@moria.home.lan> (raw)
The code that creates files and moves them to low/high inode number
files writes different file contents before doing the move - leading to
non-reproducible results.
Fix this by writing the file contents after moving them to high/low
inode number files.
Signed-off-by: Kent Overstreet <kent.overstreet@gmail.com>
---
tests/generic/544 | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/tests/generic/544 b/tests/generic/544
index 4a9f48526d..4dbaea4de0 100755
--- a/tests/generic/544
+++ b/tests/generic/544
@@ -44,8 +44,9 @@ inum() {
# Create two test files, make $low_file the file with the lower inode
# number, and make $high_file the file with the higher inode number.
create_files() {
- _pwrite_byte 0x60 0 $filesize $testdir/file1 >> $seqres.full
- _pwrite_byte 0x61 0 $filesize $testdir/file2 >> $seqres.full
+ touch $testdir/file1
+ touch $testdir/file2
+
if [ "$(inum $testdir/file1)" -lt "$(inum $testdir/file2)" ]; then
mv $testdir/file1 $low_file
mv $testdir/file2 $high_file
@@ -53,6 +54,9 @@ create_files() {
mv $testdir/file2 $low_file
mv $testdir/file1 $high_file
fi
+
+ _pwrite_byte 0x60 0 $filesize $low_file >> $seqres.full
+ _pwrite_byte 0x61 0 $filesize $high_file >> $seqres.full
}
# Check md5sum of both files, but keep results sorted by inode order
--
2.33.1
next reply other threads:[~2021-11-13 21:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-13 21:00 Kent Overstreet [this message]
2021-11-15 17:41 ` [PATCH] generic/544: Fix inode number ordering code Darrick J. Wong
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=YZAnUyyKgaddwOQH@moria.home.lan \
--to=kent.overstreet@gmail.com \
--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