From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: "Cyril Hrubis" <chrubis@suse.cz>,
"Andrea Cervesato" <andrea.cervesato@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2 03/10] setxattr01: add setxattrat variant
Date: Tue, 07 Oct 2025 15:16:00 +0200 [thread overview]
Message-ID: <DDC49J0CRCSN.3K67TAS5U4VES@suse.com> (raw)
In-Reply-To: <aOUHqfyqp8IVne7S@yuki.lan>
On Tue Oct 7, 2025 at 2:29 PM CEST, Cyril Hrubis wrote:
> Can we please, in a subsequent patch, convert this part to our standard
> approach where we check for the availability in the test setup and
> expect the syscalls to be present if kernel is new enough?
What do you think it's the best way? Some of these tests have multiple
syscalls related to *xattrat and in this test in particular we are
testing 2 syscalls. Maybe the best way would be to check for HAVE_FUNC_*
declarations in this case, but then fallback function would fail anyway.
--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-10-07 13:16 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 6:46 [LTP] [PATCH v2 00/10] setxattrat coverage Andrea Cervesato
2025-10-07 6:46 ` [LTP] [PATCH v2 01/10] lapi: add struct xattr_args fallback Andrea Cervesato
2025-10-07 11:50 ` Cyril Hrubis
2025-10-07 6:46 ` [LTP] [PATCH v2 02/10] lapi: add setxattrat() fallback definition Andrea Cervesato
2025-10-07 12:05 ` Cyril Hrubis
2025-10-07 15:16 ` Cyril Hrubis
2025-10-07 6:46 ` [LTP] [PATCH v2 03/10] setxattr01: add setxattrat variant Andrea Cervesato
2025-10-07 12:29 ` Cyril Hrubis
2025-10-07 13:16 ` Andrea Cervesato via ltp [this message]
2025-10-07 14:35 ` Cyril Hrubis
2025-10-08 10:40 ` Andrea Cervesato via ltp
2025-10-08 12:16 ` Cyril Hrubis
2025-10-07 6:46 ` [LTP] [PATCH v2 04/10] setxattr02: " Andrea Cervesato
2025-10-07 12:40 ` Cyril Hrubis
2025-10-07 6:46 ` [LTP] [PATCH v2 05/10] setxattr03: " Andrea Cervesato
2025-10-07 15:11 ` Cyril Hrubis
2025-10-07 6:46 ` [LTP] [PATCH v2 06/10] lapi: add getxattrat() fallback Andrea Cervesato
2025-10-07 15:21 ` Cyril Hrubis
2025-10-07 6:46 ` [LTP] [PATCH v2 07/10] lapi: add removexattrat() fallback Andrea Cervesato
2025-10-07 15:26 ` Cyril Hrubis
2025-10-07 6:47 ` [LTP] [PATCH v2 08/10] lapi: add safe *xattrat macros Andrea Cervesato
2025-10-08 9:36 ` Cyril Hrubis
2025-10-07 6:47 ` [LTP] [PATCH v2 09/10] Add setxattrat01 test Andrea Cervesato
2025-10-08 9:44 ` Cyril Hrubis
2025-10-13 7:54 ` Andrea Cervesato via ltp
2025-10-07 6:47 ` [LTP] [PATCH v2 10/10] Add setxattrat02 test Andrea Cervesato
2025-10-08 10:02 ` Cyril Hrubis
2025-10-10 11:05 ` Andrea Cervesato 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=DDC49J0CRCSN.3K67TAS5U4VES@suse.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=andrea.cervesato@suse.de \
--cc=chrubis@suse.cz \
/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.