From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v3 1/2] tst_filesystems01.c: Add test for .filesystems
Date: Wed, 12 Nov 2025 13:21:26 +0100 [thread overview]
Message-ID: <20251112122126.GB80114@pevik> (raw)
In-Reply-To: <aRRiLUyES4M5qjOm@yuki.lan>
> Hi!
> > > > > +static void do_test(void)
> > > > > +{
> > > > > + long fs_type;
> > > > > +
> > > > > + fs_type = tst_fs_type(MOUNT_POINT);
> > > > > +
> > > > > + if (fs_type == TST_EXT234_MAGIC) {
> > > > > + TST_EXP_PASS((check_inode_size(128)));
> > > > > + TST_EXP_PASS((check_mkfs_size_opt(10240)));
> > > > very nit: I would personally add #define for 128 and 10240, but sure it's ok to
> > > > keep it hardcoded on 2 places.
> > > I thought also use #define but i found and can not replace it in
> > > "mkfs_opts = (const char *const []){"-I", "128", "-b", "1024", NULL}",
> > > so i keep hardcoded number here.
> > Thanks for info. Sure, no problem.
> > Cc Cyril in case it's worth to fix it in metaparse.c.
> The metaparse tool does macro expansion, that shouldn't be a problem.
> Also metaparse only scans testcases/ directory during the build. The
> lib/ directory is not parsed at all.
@Cyril Ah, I'm sorry I forget it's a library test, not an ordinary test.
@Wei I thought tested and see the problem, but you probably just suspect it
would be a problem.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-11-12 12:21 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 10:51 [LTP] [PATCH v1] tst_filesystems01.c: Add test for .filesystems Wei Gao via ltp
2025-09-16 11:02 ` Petr Vorel
2025-09-24 8:42 ` [LTP] [PATCH v2] " Wei Gao via ltp
2025-10-30 20:17 ` Petr Vorel
2025-10-31 6:33 ` Wei Gao via ltp
2025-10-31 9:13 ` Petr Vorel
2025-11-01 1:20 ` [LTP] [PATCH v3 0/2] " Wei Gao via ltp
2025-11-01 1:20 ` [LTP] [PATCH v3 1/2] " Wei Gao via ltp
2025-11-11 12:06 ` Petr Vorel
2025-11-12 6:51 ` Wei Gao via ltp
2025-11-12 9:22 ` Petr Vorel
2025-11-12 10:32 ` Cyril Hrubis
2025-11-12 11:34 ` Wei Gao via ltp
2025-11-12 11:44 ` Cyril Hrubis
2025-11-12 12:14 ` Wei Gao via ltp
2025-11-12 12:21 ` Petr Vorel [this message]
2025-11-13 1:28 ` Wei Gao via ltp
2025-11-01 1:20 ` [LTP] [PATCH v3 2/2] tst_format_device.sh: Add e2fsprogs package for CI test Wei Gao via ltp
2025-11-11 12:22 ` Petr Vorel
2025-11-13 1:52 ` [LTP] [PATCH v4 0/3] tst_filesystems01.c: Add test for .filesystems Wei Gao via ltp
2025-11-13 1:52 ` [LTP] [PATCH v4 1/3] " Wei Gao via ltp
2026-01-22 3:37 ` Li Wang via ltp
2026-01-22 8:02 ` Petr Vorel
2026-01-22 8:54 ` Wei Gao via ltp
2025-11-13 1:52 ` [LTP] [PATCH v4 2/3] ci: Add mount operation for busybox Wei Gao via ltp
2025-11-13 1:52 ` [LTP] [PATCH v4 3/3] ci: Add e2fsprogs package for CI test Wei Gao via ltp
2025-12-18 13:49 ` Andrea Cervesato via ltp
2025-12-18 13:51 ` Andrea Cervesato via ltp
2026-01-23 2:36 ` [LTP] [PATCH v5 0/3] tst_filesystems01.c: Add test for .filesystems Wei Gao via ltp
2026-01-23 2:36 ` [LTP] [PATCH v5 1/3] " Wei Gao via ltp
2026-01-28 0:49 ` Li Wang via ltp
2026-01-23 2:36 ` [LTP] [PATCH v5 2/3] ci: Add mount operation for busybox Wei Gao via ltp
2026-01-23 2:36 ` [LTP] [PATCH v5 3/3] ci: Add e2fsprogs package for CI test Wei Gao 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=20251112122126.GB80114@pevik \
--to=pvorel@suse.cz \
--cc=chrubis@suse.cz \
--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