From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] syscalls/fspick: Call fsconfig with FSCONFIG_CMD_RECONFIGURE
Date: Fri, 20 Mar 2020 13:04:29 +0100 [thread overview]
Message-ID: <20200320120429.GA31021@dell5510> (raw)
In-Reply-To: <b392569b582f264927f2fea65bf14a89c03faaa5.1584679961.git.viresh.kumar@linaro.org>
Hi Viresh,
> Make sure mountpoint is reconfigured after all the recent changes by
> calling fsconfig() with FSCONFIG_CMD_RECONFIGURE.
Thanks, merged.
BTW how about print flag on failure? (just to improve readability, although
there are line numbers so not required).
Kind regards,
Petr
diff --git testcases/kernel/syscalls/fspick/fspick01.c testcases/kernel/syscalls/fspick/fspick01.c
index b5a35bf61..c84723805 100644
--- testcases/kernel/syscalls/fspick/fspick01.c
+++ testcases/kernel/syscalls/fspick/fspick01.c
@@ -33,19 +33,19 @@ static void run(unsigned int n)
TEST(fsconfig(fspick_fd, FSCONFIG_SET_STRING, "sync", "false", 0));
if (TST_RET == -1) {
- tst_res(TFAIL | TTERRNO, "fsconfig() failed");
+ tst_res(TFAIL | TTERRNO, "fsconfig(FSCONFIG_SET_STRING) failed");
goto out;
}
TEST(fsconfig(fspick_fd, FSCONFIG_SET_FLAG, "ro", NULL, 0));
if (TST_RET == -1) {
- tst_res(TFAIL | TTERRNO, "fsconfig() failed");
+ tst_res(TFAIL | TTERRNO, "fsconfig(FSCONFIG_SET_FLAG) failed");
goto out;
}
TEST(fsconfig(fspick_fd, FSCONFIG_CMD_RECONFIGURE, NULL, NULL, 0));
if (TST_RET == -1) {
- tst_res(TFAIL | TTERRNO, "fsconfig() failed");
+ tst_res(TFAIL | TTERRNO, "fsconfig(FSCONFIG_CMD_RECONFIGURE) failed");
goto out;
}
next prev parent reply other threads:[~2020-03-20 12:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 4:52 [LTP] [PATCH] syscalls/fspick: Call fsconfig with FSCONFIG_CMD_RECONFIGURE Viresh Kumar
2020-03-20 12:04 ` Petr Vorel [this message]
2020-03-23 3:14 ` Viresh Kumar
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=20200320120429.GA31021@dell5510 \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/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