From: Petr Vorel <pvorel@suse.cz>
To: Matt Ochs <mochs@nvidia.com>
Cc: "ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH] syscalls: file_attr05: skip ntfs filesystem
Date: Thu, 16 Apr 2026 10:50:53 +0200 [thread overview]
Message-ID: <20260416085053.GA290566@pevik> (raw)
In-Reply-To: <79CF2D7E-5987-4321-BDE7-D5FF34EBF952@nvidia.com>
Hi Matt
> Hi Petr,
> > On Apr 9, 2026, at 02:53, Petr Vorel <pvorel@suse.cz> wrote:
> > Hi Matthew,
> >> LTP mounts ntfs via ntfs-3g (FUSE) rather than the kernel ntfs3
> >> driver. ntfs-3g's ntfs_ioctl() returns EINVAL for any unhandled
> >> ioctl, including FS_IOC_FSSETXATTR, so file_setattr() returns
> >> EINVAL instead of the expected EOPNOTSUPP.
> >> Add "ntfs" to skip_filesystems for the same reason "fuse" is
> >> already skipped.
> > Reviewed-by: Petr Vorel <pvorel@suse.cz>
> > Good catch, thanks!
> I appreciate the review!
You're welcome, thanks for your contributions!
> > We did not notice, because we have ntfs3 blacklisted in openSUSE Tumbleweed:
...
> >> diff --git a/testcases/kernel/syscalls/file_attr/file_attr05.c b/testcases/kernel/syscalls/file_attr/file_attr05.c
> >> index 6c1471da33e7..85b6cafc5f17 100644
> >> --- a/testcases/kernel/syscalls/file_attr/file_attr05.c
> >> +++ b/testcases/kernel/syscalls/file_attr/file_attr05.c
> >> @@ -49,6 +49,7 @@ static struct tst_test test = {
> >> .skip_filesystems = (const char *const []) {
> >> "xfs",
> >> "fuse", /* EINVAL is raised before EOPNOTSUPP */
> >> + "ntfs", /* mounted via ntfs-3g (FUSE), returns EINVAL */
> > For me it'd work to replace "fuse" with "ntfs" (i.e. remove "fuse").
> > Does it work for you as well, or you need to have blacklisted both?
> Regarding replacing "fuse" with "ntfs": on Ubuntu, ntfs3 is available
> as a kernel module, so the detection reports "Kernel supports ntfs”
> and the FUSE skip path never fires — meaning "fuse" alone doesn’t
> catch it. Removing "fuse" would also drop coverage of other
> FUSE-based filesystems, so I'd prefer to keep both entries.
I actually think that other fuse implementations work, fuse was probably added
to fix ntfs. Or am I wrong? But that can be solved as a separate effort, I don't
want to block what you plan to fix.
Kind regards,
Petr
> -matt
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-04-16 8:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 17:44 [LTP] [PATCH] syscalls: file_attr05: skip ntfs filesystem Matthew R. Ochs via ltp
2026-04-09 7:53 ` Petr Vorel
2026-04-09 22:55 ` Matt Ochs via ltp
2026-04-16 8:50 ` Petr Vorel [this message]
2026-04-09 8:27 ` Cyril Hrubis
2026-04-09 22:51 ` Matt Ochs via ltp
2026-04-10 10:04 ` Cyril Hrubis
2026-04-10 16:42 ` Matt Ochs via ltp
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=20260416085053.GA290566@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=mochs@nvidia.com \
/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