From: Avinesh Kumar <akumar@suse.de>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/1] fsconfig03: Skip on FUSE
Date: Fri, 31 Mar 2023 21:04:53 +0530 [thread overview]
Message-ID: <2956694.zlGccA3lKM@localhost> (raw)
In-Reply-To: <20230328144031.791212-1-pvorel@suse.cz>
Hi Petr,
Reviewed-by: Avinesh Kumar <akumar@suse.de>
Tested-by: Avinesh Kumar <akumar@suse.de>
On Tuesday, March 28, 2023 8:10:31 PM IST Petr Vorel wrote:
> fsconfig03 is broken not only on vfat and ntfs, but also over FUSE:
>
> tst_supported_fs_types.c:120: TINFO: FUSE does support exfat
> tst_supported_fs_types.c:55: TINFO: mkfs.exfat does exist
> ...
> tst_test.c:1634: TINFO: === Testing on exfat ===
> tst_test.c:1093: TINFO: Formatting /dev/loop0 with exfat opts='' extra opts=''
> fsconfig03.c:38: TBROK: fsopen() failed: ENODEV (19)
I could also reproduce this failure when running FUSE implementation of exfat.
And tested the patch which takes care of it.
>
> NOTE: it actually works on vfat which is not over FUSE:
Yes, test works fine on vfat.
> tst_supported_fs_types.c:90: TINFO: Kernel supports vfat
> tst_supported_fs_types.c:55: TINFO: mkfs.vfat does exist
> ...
> tst_test.c:1634: TINFO: === Testing on vfat ===
> tst_test.c:1093: TINFO: Formatting /dev/loop0 with vfat opts='' extra opts=''
> fsconfig03.c:72: TPASS: kernel seems to be fine on vfat
>
> Reported-by: Wei Gao <wegao@suse.com>
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
> ---
> Verifying NTFS as kernel module (I'd be surprised if it was not
> working). The setup is the same as for fsconfig01.c (fsconfig02.c is for
> expected errors, thus has less strict requirements).
>
> Kind regards,
> Petr
>
> testcases/kernel/syscalls/fsconfig/fsconfig03.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/testcases/kernel/syscalls/fsconfig/fsconfig03.c b/testcases/kernel/syscalls/fsconfig/fsconfig03.c
> index e891c9f98..0ba5355d3 100644
> --- a/testcases/kernel/syscalls/fsconfig/fsconfig03.c
> +++ b/testcases/kernel/syscalls/fsconfig/fsconfig03.c
> @@ -88,7 +88,7 @@ static struct tst_test test = {
> .mntpoint = MNTPOINT,
> .all_filesystems = 1,
> .taint_check = TST_TAINT_W | TST_TAINT_D,
> - .skip_filesystems = (const char *const []){"ntfs", "vfat", NULL},
> + .skip_filesystems = (const char *const []){"fuse", NULL},
> .tags = (const struct tst_tag[]) {
> {"linux-git", "722d94847de29"},
> {"CVE", "2022-0185"},
>
Regards,
Avinesh
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-03-31 15:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 14:40 [LTP] [PATCH 1/1] fsconfig03: Skip on FUSE Petr Vorel
2023-03-29 11:58 ` Wei Gao via ltp
2023-03-29 13:38 ` Petr Vorel
2023-03-30 14:14 ` Wei Gao via ltp
2023-03-31 15:34 ` Avinesh Kumar [this message]
2023-04-03 5:55 ` 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=2956694.zlGccA3lKM@localhost \
--to=akumar@suse.de \
--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).