From: Nikolay Borisov <nborisov@suse.com>
To: fstests@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org, Nikolay Borisov <nborisov@suse.com>
Subject: [PATCH 1/2] common/renameat2: Make _rename_tests_source_dest take flags as 4th arguement
Date: Mon, 30 Aug 2021 15:23:05 +0300 [thread overview]
Message-ID: <20210830122306.882081-1-nborisov@suse.com> (raw)
Currently this function takes the flags parameter to be passed to the
renameat program by assuming there exists a 'flags' variable. Instead,
make the flags being passed as 4th argument to the function.
Signed-off-by: Nikolay Borisov <nborisov@suse.com>
---
common/renameat2 | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/common/renameat2 b/common/renameat2
index 4b64eea7824b..4d25d7cebf94 100644
--- a/common/renameat2
+++ b/common/renameat2
@@ -61,6 +61,7 @@ _rename_tests_source_dest()
local source=$1
local dest=$2
local options=$3
+ local flags=$4
for stype in none regu symb dire tree; do
for dtype in none regu symb dire tree; do
@@ -90,11 +91,11 @@ _rename_tests()
local flags=$2
#same directory renames
- _rename_tests_source_dest $testdir/src $testdir/dst "samedir "
+ _rename_tests_source_dest $testdir/src $testdir/dst "samedir " $flags
#cross directory renames
mkdir $testdir/x $testdir/y
- _rename_tests_source_dest $testdir/x/src $testdir/y/dst "crossdir"
+ _rename_tests_source_dest $testdir/x/src $testdir/y/dst "crossdir" $flags
rmdir $testdir/x $testdir/y
}
--
2.17.1
next reply other threads:[~2021-08-30 12:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 12:23 Nikolay Borisov [this message]
2021-08-30 12:23 ` [PATCH V2 2/2] btrfs: Add test for rename/exchange behavior between subvolumes Nikolay Borisov
2021-08-30 15:01 ` Filipe Manana
2021-08-30 15:03 ` Filipe Manana
2021-08-30 15:34 ` Nikolay Borisov
2021-08-30 15:36 ` [PATCH v2] " Nikolay Borisov
2021-09-03 16:23 ` Filipe Manana
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=20210830122306.882081-1-nborisov@suse.com \
--to=nborisov@suse.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@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