From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] utimensat01: Test all available FS and handle FS with no attributes
Date: Wed, 30 Sep 2020 10:21:47 +0200 [thread overview]
Message-ID: <20200930082147.GA16382@dell5510> (raw)
In-Reply-To: <20200930081655.GA6611@yuki.lan>
Hi Cyril,
> Hi!
> > Although this fails on NTFS and exfat and FUSE.
> > I don't remember which flag removes these filesystems, there was some
> > workaround. Cyril, Li, Jan, do you remember?
> That's the:
> .dev_fs_flags = TST_FS_SKIP_FUSE,
> Which should fix the failures here. Moreover I do wonder if this is a
> real bug in the fuse implementation or something that have been left out
> intentionally.
Thanks for info. Also vfat needs to be filtered out (if it's not a bug, which
needs to be implemented).
If we decide to filter out it, we'd need one more flag (something like
TST_FS_SKIP_MICROSOFT, which would filter out vfat, ntfs and exfat).
Kind regards,
Petr
next prev parent reply other threads:[~2020-09-30 8:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 14:46 [LTP] [PATCH] utimensat01: Test all available FS and handle FS with no attributes Richard Palethorpe
2020-09-29 18:11 ` Petr Vorel
2020-09-30 8:16 ` Cyril Hrubis
2020-09-30 8:21 ` Petr Vorel [this message]
2020-09-30 11:24 ` Richard Palethorpe
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=20200930082147.GA16382@dell5510 \
--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