From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: "Wei Gao" <wegao@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v6] fsconfig04: Check FSCONFIG_SET_PATH
Date: Tue, 09 Jun 2026 09:44:27 +0000 [thread overview]
Message-ID: <6a27e07c.159d33f9.2309c6.d93e@mx.google.com> (raw)
In-Reply-To: <20260430051915.2178-1-wegao@suse.com>
Hi Wei,
> The fsconfig01.c does not test if FSCONFIG_SET_PATH have any effect,
> most of the calls there just set dummy "sync" parameter. This test
> case aims to verify if the FSCONFIG_SET_PATH operation can be used
> to dynamically change the external journal device of ext3 or ext4
> filesystem.
>
> Fixes: https://github.com/linux-test-project/ltp/issues/1169
This should be Closes:
> +
> +/*\
> + * This test aims to validate the functionality of fsconfig(FSCONFIG_SET_PATH) in
We need man syntax here, so we can have manual link in the test catalog.
:manpage:`fsconfig(2)`
> +static void setup(void)
> +{
We neeed fsopen_supported_by_kernel() here.
> + strcpy(dev0, tst_device->dev);
> +
I think we are mixing too many things here. tst_brk() should be used
with TBROK and TFAIL should be followed by a return. Use TFAIL for the
tested feature and TBROK for everything else.
Regards,
--
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:[~2026-06-09 9:44 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 15:10 [LTP] [PATCH v1] fsconfig04.c: Check FSCONFIG_SET_PATH Wei Gao via ltp
2025-05-22 20:56 ` Petr Vorel
2025-05-26 14:29 ` Wei Gao via ltp
2025-05-26 6:40 ` Petr Vorel
2025-05-26 14:35 ` [LTP] [PATCH v2] " Wei Gao via ltp
2025-05-26 9:54 ` Petr Vorel
2025-05-26 12:54 ` Cyril Hrubis
2025-05-26 16:13 ` Petr Vorel
2025-05-27 8:24 ` Cyril Hrubis
2025-05-27 8:58 ` [LTP] LTP doc: test examples [was: Re: [PATCH v2] fsconfig04.c: Check FSCONFIG_SET_PATH] Petr Vorel
2025-05-26 14:38 ` [LTP] [PATCH v2] fsconfig04.c: Check FSCONFIG_SET_PATH Cyril Hrubis
2025-06-03 21:45 ` [LTP] [PATCH v3] " Wei Gao via ltp
2025-10-17 4:39 ` Wei Gao via ltp
2025-12-12 9:29 ` Andrea Cervesato via ltp
2026-02-25 9:27 ` Wei Gao via ltp
2026-03-16 8:49 ` Petr Vorel
2026-03-17 0:59 ` Wei Gao via ltp
2026-03-24 12:50 ` Petr Vorel
2026-04-10 5:47 ` [LTP] [PATCH v4] " Wei Gao via ltp
2026-04-16 11:25 ` [LTP] [PATCH v5] fsconfig04: " Wei Gao via ltp
2026-04-16 13:52 ` [LTP] " linuxtestproject.agent
2026-04-16 13:55 ` Andrea Cervesato via ltp
2026-04-30 5:19 ` [LTP] [PATCH v6] " Wei Gao via ltp
2026-04-30 6:34 ` [LTP] " linuxtestproject.agent
2026-05-07 12:25 ` Wei Gao via ltp
2026-06-09 9:44 ` Andrea Cervesato via ltp [this message]
2026-06-10 5:21 ` [LTP] [PATCH v7] " Wei Gao via ltp
2026-06-10 10:06 ` [LTP] " linuxtestproject.agent
2026-06-18 2:38 ` [LTP] [PATCH v8] " Wei Gao via ltp
2026-06-18 4:04 ` [LTP] " linuxtestproject.agent
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=6a27e07c.159d33f9.2309c6.d93e@mx.google.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=wegao@suse.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