From: Xiao Yang <yangx.jy@cn.fujitsu.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] lib/tst_test.c: set mount_device amd format_device of all_filesystems is set
Date: Tue, 4 Jun 2019 16:09:58 +0800 [thread overview]
Message-ID: <5CF62756.3000608@cn.fujitsu.com> (raw)
In-Reply-To: <20190604074035.4523-1-xzhou@redhat.com>
On 2019/06/04 15:40, Murphy Zhou wrote:
> preadv203.c does not set mount_device, which makes BROK:
> preadv203.c:122: BROK: preadv2() failed: EOPNOTSUPP
>
> Fixing this by format and mount device if all_filesystems is set in library.
>
> Signed-off-by: Murphy Zhou<xzhou@redhat.com>
> ---
> lib/tst_test.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/lib/tst_test.c b/lib/tst_test.c
> index 95f389d2e..61dba793e 100644
> --- a/lib/tst_test.c
> +++ b/lib/tst_test.c
> @@ -808,8 +808,11 @@ static void do_setup(int argc, char *argv[])
> tst_test->format_device = 1;
> }
>
> - if (tst_test->all_filesystems)
> + if (tst_test->all_filesystems) {
> tst_test->needs_device = 1;
> + tst_test->mount_device = 1;
> + tst_test->format_device = 1;
> + }
Hi Murph,
1) tst_test->format_device will be set automatically when we set
tst_test->mount_device.
2) It's unreasonable to set tst_test->mount_device for all filesystems
forcely because we
don't need to mount for all filesystems in some cases(e.g. just test
formating).
Perhaps, you just add tst_test->mount_device in preadv203.c. :-)
Best Regards,
Xiao Yang
>
> setup_ipc();
>
next prev parent reply other threads:[~2019-06-04 8:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 7:40 [LTP] [PATCH] lib/tst_test.c: set mount_device amd format_device of all_filesystems is set Murphy Zhou
2019-06-04 8:09 ` Xiao Yang [this message]
2019-06-04 8:23 ` Murphy Zhou
2019-06-05 4:42 ` [LTP] [PATCH v2] syscalls/preadv2/preadv203: set mount_device flag Murphy Zhou
2019-06-05 5:19 ` Xiao Yang
2019-06-05 5:27 ` Murphy Zhou
2019-06-05 5:33 ` [LTP] [PATCH v3] " Murphy Zhou
2019-06-05 5:55 ` Xiao Yang
2019-06-05 14:06 ` Cyril Hrubis
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=5CF62756.3000608@cn.fujitsu.com \
--to=yangx.jy@cn.fujitsu.com \
--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