From: Petr Vorel <pvorel@suse.cz>
To: Anders Roxell <anders.roxell@linaro.org>
Cc: benjamin.copeland@linaro.org, dan.carpenter@linaro.org,
ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] file_attr02: Add XFS kernel config requirement
Date: Fri, 24 Oct 2025 15:30:35 +0200 [thread overview]
Message-ID: <20251024133035.GA590258@pevik> (raw)
In-Reply-To: <20251024125613.2340799-1-anders.roxell@linaro.org>
> The file_attr02 test requires XFS filesystem support to properly
> test the FS_IOC_FSSETXATTR ioctl with project quotas. Add the
> XFS kernel configuration requirement to ensure the test can run
> on systems with XFS support either built-in or as a module.
So you have problem on the kernel with CONFIG_XFS_FS=y?
I wonder why tst_get_supported_fs_types() from lib/tst_supported_fs_types.c did
not detect it. Could you please post whole output?
Because if code in struct tst_test.filesystems does not work, many tests would
be affected with this setup. I'm probably missing something, but I'd prefer to
fix the detection in the library than force config (we don't have any CONFIG_.*_FS
in testcases/).
> Suggested-by: Dan Carpenter <dan.carpenter@linaro.org>
> Signed-off-by: Anders Roxell <anders.roxell@linaro.org>
> ---
> testcases/kernel/syscalls/file_attr/file_attr02.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
> diff --git a/testcases/kernel/syscalls/file_attr/file_attr02.c b/testcases/kernel/syscalls/file_attr/file_attr02.c
> index f6625985a514..0ad57177078b 100644
> --- a/testcases/kernel/syscalls/file_attr/file_attr02.c
> +++ b/testcases/kernel/syscalls/file_attr/file_attr02.c
> @@ -18,6 +18,11 @@
> #define BLOCKS 128
> #define PROJID 16
> +static const char *kconfigs[] = {
> + "CONFIG_XFS_FS=y | CONFIG_XFS_FS=m",
> + NULL
> +};
> +
> static int fd = -1;
> static int dfd = -1;
> static struct fsxattr xattr;
> @@ -105,5 +110,6 @@ static struct tst_test test = {
> .bufs = (struct tst_buffers []) {
> {&attr, .size = sizeof(struct file_attr)},
> {}
> - }
> + },
> + .needs_kconfigs = kconfigs,
very nit: we usually use anonymous definition here, instead creating static
variable kconfigs[].
Kind regards,
Petr
> };
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-10-24 13:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 12:56 [LTP] [PATCH] file_attr02: Add XFS kernel config requirement Anders Roxell
2025-10-24 13:30 ` Petr Vorel [this message]
2025-10-24 17:25 ` Dan Carpenter
2025-10-27 9:21 ` Cyril Hrubis
2025-10-27 14:32 ` Anders Roxell
2025-10-27 15:11 ` Cyril Hrubis
2025-10-27 15:19 ` Dan Carpenter
2025-10-30 18:24 ` Petr Vorel
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=20251024133035.GA590258@pevik \
--to=pvorel@suse.cz \
--cc=anders.roxell@linaro.org \
--cc=benjamin.copeland@linaro.org \
--cc=dan.carpenter@linaro.org \
--cc=ltp@lists.linux.it \
/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