From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v4] syscalls/newmount: new test case for new mount API
Date: Thu, 23 Jan 2020 14:15:22 +0100 [thread overview]
Message-ID: <20200123131522.GA94750@x230> (raw)
In-Reply-To: <20200123104114.GD27845@rei>
Hi,
Cyril, thanks for review.
> > For FUSE, I think we'd better to not test FUSE by default. Then let the case decide if
> > it would like to support a FUSE fs test. Change the TST_FS_SKIP_FUSE to TST_FS_SUP_FUSE,
> > if someone case wants to test a FUSE fs (likes ntfs), it should do special steps to mount
> > it, or it'll test linux internal ntfs.ko.
> It works fine for majority of testcases, the mount() and fsmount()
> syscalls are kind of special here. I guess that all we need to do here
> is to skip the fuse here.
Great, we get back to the original suggestion, which is in v4:
.dev_fs_flags = TST_FS_SKIP_FUSE,
Kind regards,
Petr
next prev parent reply other threads:[~2020-01-23 13:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 7:56 [LTP] [PATCH v4] syscalls/newmount: new test case for new mount API Zorro Lang
2020-01-16 11:49 ` Cyril Hrubis
2020-01-16 15:08 ` Zorro Lang
2020-01-17 7:48 ` Petr Vorel
2020-01-17 11:05 ` Zorro Lang
2020-01-23 10:41 ` Cyril Hrubis
2020-01-23 13:15 ` Petr Vorel [this message]
2020-01-16 11:52 ` Petr Vorel
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=20200123131522.GA94750@x230 \
--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