From: Cyril Hrubis <chrubis@suse.cz>
To: XiaoLei Wu <wxl18715129466@gmail.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] syscalls/unlink09: report unsupported inode flags as TCONF
Date: Wed, 3 Jun 2026 11:59:02 +0200 [thread overview]
Message-ID: <ah_65vifTFw0LNy0@yuki.lan> (raw)
In-Reply-To: <20260602064442.718507-1-wxl18715129466@gmail.com>
Hi!
> If FS_IOC_GETFLAGS fails with ENOTTY, the filesystem does not support
> inode flags. This is an unsupported test configuration rather than a
> broken test setup, so report TCONF instead of TBROK.
This happens on ntfs3 as well right?
I suppose that this will be fixed if we had the change I've proposed for
the test library in the skiplist handling for the other patch.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-06-03 9:59 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 ` Cyril Hrubis [this message]
2026-06-04 8:05 ` [LTP] [PATCH] " xl wu
2026-06-04 8:36 ` Cyril Hrubis
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=ah_65vifTFw0LNy0@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