From: Li Wang <liwang@redhat.com>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/1] utime03.c: Fix filesystem name
Date: Mon, 17 Jan 2022 10:23:51 +0800 [thread overview]
Message-ID: <CAEemH2ddzfJ48prJTejCBq-=u4O-w0ENR27A_DjUo_OsqShCow@mail.gmail.com> (raw)
In-Reply-To: <20220114210034.16177-1-pvorel@suse.cz>
Hi Petr,
On Sat, Jan 15, 2022 at 5:00 AM Petr Vorel <pvorel@suse.cz> wrote:
>
> Use the same name as in tst_fs_type_name() to actually skip it.
>
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
> ---
> "v9fs is a Unix implementation of the Plan 9 9p remote filesystem
> protocol." [1]
>
> NOTE: filesystem is called v9fs, but mount parameter is "9p"
> that's probably the reason why named "9p" and not "v9" in
> tst_fs_type_name().
>
> Kind regards,
> Petr
>
> [1] https://www.kernel.org/doc/html/latest/filesystems/9p.html
>
> testcases/kernel/syscalls/utime/utime03.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/testcases/kernel/syscalls/utime/utime03.c b/testcases/kernel/syscalls/utime/utime03.c
> index 48cc3bae77..823bc5f72a 100644
> --- a/testcases/kernel/syscalls/utime/utime03.c
> +++ b/testcases/kernel/syscalls/utime/utime03.c
> @@ -93,7 +93,7 @@ static struct tst_test test = {
> .mntpoint = MNTPOINT,
> .all_filesystems = 1,
> .skip_filesystems = (const char *const[]) {
> - "v9",
> + "9p",
I'm wondering does it really take effect with whatever "v9" or "9p"?
Because the fs_type_whitelist[] does not include any of them.
> "vfat",
> "exfat",
> NULL
> --
> 2.34.1
>
>
> --
> Mailing list info: https://lists.linux.it/listinfo/ltp
>
--
Regards,
Li Wang
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-01-17 2:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 21:00 [LTP] [PATCH 1/1] utime03.c: Fix filesystem name Petr Vorel
2022-01-17 2:23 ` Li Wang [this message]
2022-01-17 3:13 ` Li Wang
2022-01-17 9:04 ` Petr Vorel
2022-01-18 7:24 ` Li Wang
2022-01-18 9:01 ` Petr Vorel
2022-01-18 9:11 ` Li Wang
2022-01-18 10:34 ` 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='CAEemH2ddzfJ48prJTejCBq-=u4O-w0ENR27A_DjUo_OsqShCow@mail.gmail.com' \
--to=liwang@redhat.com \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).