public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Xiao Yang <yangx.jy@cn.fujitsu.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v3] syscalls/preadv2/preadv203: set mount_device flag
Date: Wed, 5 Jun 2019 13:55:33 +0800	[thread overview]
Message-ID: <5CF75955.1090704@cn.fujitsu.com> (raw)
In-Reply-To: <20190605053312.17369-1-jencce.kernel@gmail.com>

Hi Murphy,

Pushed. Thanks for your patch. :-)

Best Regards,
Xiao Yang
On 2019/06/05 13:33, Murphy Zhou wrote:
> Now the tests are running in MOUNTPOINT without it mounted. Fails on
> NFS, cifs, tmpfs:
>
>     preadv203.c does not set mount_device, which makes BROK:
>       preadv203.c:122: BROK: preadv2() failed: EOPNOTSUPP
>
> Signed-off-by: Murphy Zhou <jencce.kernel@gmail.com>
> ---
> v3:
>   improve commit message
> v2:
>   set mount_device in preadv203.c, rather than in the library
>
>  testcases/kernel/syscalls/preadv2/preadv203.c | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/testcases/kernel/syscalls/preadv2/preadv203.c b/testcases/kernel/syscalls/preadv2/preadv203.c
> index 810d1e8db..e4f68a51b 100644
> --- a/testcases/kernel/syscalls/preadv2/preadv203.c
> +++ b/testcases/kernel/syscalls/preadv2/preadv203.c
> @@ -261,6 +261,7 @@ static struct tst_test test = {
>  	.cleanup = cleanup,
>  	.test_all = verify_preadv2,
>  	.mntpoint = MNTPOINT,
> +	.mount_device = 1,
>  	.all_filesystems = 1,
>  	.needs_tmpdir = 1,
>  	.needs_root = 1,




  reply	other threads:[~2019-06-05  5:55 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
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 [this message]
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=5CF75955.1090704@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