From: Joerg Vehlow <lkml@jv-coder.de>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v3] squashfs: Add regression test for sanity check bug
Date: Thu, 15 Jul 2021 10:44:56 +0200 [thread overview]
Message-ID: <4aaba9d9-e013-3c12-500a-647ff2c0b82d@jv-coder.de> (raw)
In-Reply-To: <60EFF034.6070800@fujitsu.com>
Hi,
On 7/15/2021 10:21 AM, xuyang2018.jy@fujitsu.com wrote:
>
>> + tst_cmd(argv, "/dev/null", NULL, 0);
> We have SAFE_CMD api.
Yes makes sense. This can be replaced during merge I guess.
-?????? tst_cmd(argv, "/dev/null", NULL, 0);
+?????? SAFE_CMD(argv, "/dev/null", NULL);
>> +static struct tst_test test = {
>> + .test_all = run,
>> + .cleanup = cleanup,
>> + .setup = setup,
>> + .needs_root = 1,
>> + .needs_device = 1,
>> + .dev_min_size = 1,
>> + .needs_cmds = (const char *const []) {
>> + "mksquashfs",
>> + NULL
>> + },
>> + .needs_drivers = (const char *const []) {
>> + "squashfs",
>> + NULL
>> + },
>> + .tags = (const struct tst_tag[]) {
>> + {"linux-git", "c1b2028315c"},
>> + {"linux-git", "8b44ca2b634"},
>> + {}
>> + },
>> + .needs_tmpdir = 1,
> needs_device has enabled needs_tmpdir in internal, so we don't need to
> set it here.
Honestly I hate implicitness like that. I think if the test itself needs
the tmpdir, it should state it and not rely on some other "needs_*"
stuff to also enable it.
But if whoever merges this agrees with you, he can change it...
Joerg
next prev parent reply other threads:[~2021-07-15 8:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 5:08 [LTP] [PATCH v3] squashfs: Add regression test for sanity check bug Joerg Vehlow
2021-07-15 8:00 ` Richard Palethorpe
2021-07-15 8:21 ` xuyang2018.jy
2021-07-15 8:44 ` Joerg Vehlow [this message]
2021-07-15 9:27 ` Cyril Hrubis
2021-07-15 10:12 ` Joerg Vehlow
2021-07-15 10:09 ` Cyril Hrubis
2021-07-15 10:40 ` Joerg Vehlow
2021-07-21 11:47 ` Cyril Hrubis
2021-08-04 14:05 ` Cyril Hrubis
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=4aaba9d9-e013-3c12-500a-647ff2c0b82d@jv-coder.de \
--to=lkml@jv-coder.de \
--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