Linux Test Project
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: xl wu <wxl18715129466@gmail.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] syscalls/unlink09: report unsupported inode flags as TCONF
Date: Thu, 4 Jun 2026 10:36:40 +0200	[thread overview]
Message-ID: <aiE5GFLKJ_q7NEK5@yuki.lan> (raw)
In-Reply-To: <CANJThoG6kuQ7tAqMr3JVMuu7qu8QZXMqDTU27skohpB37k8xJg@mail.gmail.com>

Hi!
>   yes, this was triggered on ntfs3 in my testing.
> 
>   If the skiplist change makes tests that skip ntfs skip ntfs3 as well,
>   then this particular failure would be covered.
> 
>   I still wonder if unlink09 should treat ENOTTY from FS_IOC_GETFLAGS as
>   TCONF in general, though. That would cover any filesystem where inode
>   flags are not supported, not just ntfs3.

If we do that we would miss a bug when the support would be disabled by
a mistake in one of the filesystems. So as long as the filesystems that
lack the support are filtered out it's better to make sure that the
functionality is there unconditionally.

-- 
Cyril Hrubis
chrubis@suse.cz

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

  reply	other threads:[~2026-06-04  8:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-02  6:44 [LTP] [PATCH] syscalls/unlink09: report unsupported inode flags as TCONF XiaoLei Wu
2026-06-02 11:23 ` [LTP] " linuxtestproject.agent
2026-06-03  9:59 ` [LTP] [PATCH] " Cyril Hrubis
2026-06-04  8:05   ` xl wu
2026-06-04  8:36     ` Cyril Hrubis [this message]
2026-06-04 10:00       ` xl wu
  -- strict thread matches above, loose matches on Subject: below --
2026-06-02  6:14 XiaoLei Wu

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=aiE5GFLKJ_q7NEK5@yuki.lan \
    --to=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=wxl18715129466@gmail.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