From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: "Wei Gao via ltp" <ltp@lists.linux.it>
Cc: ltp@lists.linux.it, linuxtestproject.agent@gmail.com
Subject: Re: [LTP] fsconfig04: Check FSCONFIG_SET_PATH
Date: Tue, 11 Aug 2026 07:44:26 +0000 [thread overview]
Message-ID: <6a7ad2db.a148a86f.110d56.d1c6@mx.google.com> (raw)
In-Reply-To: <anKp5GokntftzFa3@autotest-wegao.qe.prg2.suse.org>
Hi Wei,
> > > + TEST(fsconfig(fd, FSCONFIG_SET_PATH, "journal_path", dev2, 0));
> > > + if (TST_RET == -1) {
> > > + if (TST_ERR == EOPNOTSUPP)
> > > + tst_brk(TCONF, "fsconfig(FSCONFIG_SET_PATH) not supported");
> > > + else
> > > + tst_brk(TFAIL | TTERRNO, "fsconfig(FSCONFIG_SET_PATH) failed");
> > > + }
> >
> > Could this test be gated with .min_kver = "7.2"?
> >
> > Before Linux 7.2, ext4 declared journal_path as a string parameter, so
> > FSCONFIG_SET_PATH is rejected with EINVAL rather than EOPNOTSUPP. Since
> > fsopen_supported_by_kernel() only gates fsopen at Linux 5.2, those kernels
> > reach the else branch and report TFAIL instead of TCONF.
> If fsconfig parameter is correct, return EINVAL should be an kernel bug.
> Current logic is correct.
> I guess AI mix wtih some old code with new API. But how to fix AI's rule is a
> question.
yeah, agent is wrong.
> >
> > > + SAFE_SSCANF(dev2, "/dev/%s", loop_name);
> > > +
> > > + snprintf(path, sizeof(path), "/sys/block/%s/dev", loop_name);
> > > + SAFE_FILE_SCANF(path, "%u:%u", &major, &minor);
> >
> > Could the device number be obtained from stat(dev2).st_rdev instead?
what about this?
> >
> > tst_find_free_loopdev() also supports /dev/loop/N and /dev/block/loopN.
> > Those paths produce loop/N or block/loopN here, causing the test to read a
> > nonexistent sysfs path and terminate with TBROK.
> >
> > > + SAFE_MKFS(dev0, tst_device->fs_type, mkfs_opts_set_journal_dev1, NULL);
> > > +}
> > > +
> > > +static void run(void)
> > > +{
> > > + ...
> > > + TEST(fsconfig(fd, FSCONFIG_SET_PATH, "journal_path", dev2, 0));
> >
> > Could each iteration reset dev0 to dev1 or alternate the source and target
> > journal devices?
> >
> > The first iteration persists dev2 in dev0's superblock. Every subsequent
> > -i iteration requests dev2 again, so it no longer exercises a dynamic
> > journal-device change.
and this?
--
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-08-11 7:44 UTC|newest]
Thread overview: 42+ 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 ` [LTP] [PATCH v6] " Andrea Cervesato via ltp
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
2026-06-26 6:14 ` [LTP] [PATCH v9] " Wei Gao via ltp
2026-06-26 9:33 ` [LTP] " linuxtestproject.agent
2026-07-13 12:08 ` [LTP] [PATCH v9] " Andrea Cervesato via ltp
2026-07-20 12:26 ` [LTP] [PATCH v10] " Wei Gao via ltp
2026-07-20 13:11 ` [LTP] " linuxtestproject.agent
2026-08-03 2:12 ` [LTP] [PATCH v11] " Wei Gao via ltp
2026-08-03 3:37 ` [LTP] " linuxtestproject.agent
2026-08-04 1:04 ` [LTP] [PATCH v12] " Wei Gao via ltp
2026-08-04 4:17 ` [LTP] " linuxtestproject.agent
2026-08-05 3:11 ` Wei Gao via ltp
2026-08-11 7:44 ` Andrea Cervesato via ltp [this message]
2026-08-06 11:30 ` [LTP] [PATCH v12] " 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=6a7ad2db.a148a86f.110d56.d1c6@mx.google.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=linuxtestproject.agent@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