All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: "Matthew R. Ochs" <mochs@nvidia.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] syscalls: file_attr05: skip ntfs filesystem
Date: Thu, 9 Apr 2026 10:27:57 +0200	[thread overview]
Message-ID: <addjDV_wbPgD0y8e@yuki.lan> (raw)
In-Reply-To: <20260408174406.1572520-1-mochs@nvidia.com>

Hi!
> 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.

The "fuse" in skiplist should match all fuse based filesystems. We pass
the skip_filesystems pointer to tst_get_supported_fs_types() in
lib/tst_supported_fs_types.c. If "fuse" is present there we enable
skip_fuse flag nad pass it to fs_could_be_used() function. In the
fs_could_be_used() we check if filesystem is implemented by fuse and
then skip it accordingly.

When I run the test I see:

...
tst_supported_fs_types.c:165: TINFO: Skipping FUSE based ntfs as requested by the test
...

So likely something else is at play here. Are you sure you are dealing
with a fuse based ntfs or with the kernel based implementation?

-- 
Cyril Hrubis
chrubis@suse.cz

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  parent reply	other threads:[~2026-04-09  8:28 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
2026-04-09  8:27 ` Cyril Hrubis [this message]
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=addjDV_wbPgD0y8e@yuki.lan \
    --to=chrubis@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.