From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2] squashfs: Add regression test for sanity check bug
Date: Wed, 14 Jul 2021 10:40:01 +0200 [thread overview]
Message-ID: <YO6i4QqnULLpsoZv@yuki> (raw)
In-Reply-To: <dc6520e5-5bc3-b277-c33a-a553632e27a5@jv-coder.de>
Hi!
> >> + * [DESCRIPTION]
> > I think it is [Description] now.
> Both seem to work and there is no documentation for this.
> But looks the lower case variant is used more often. Will update this
> for v3.
I started with uppercase but then everybody else decided that only first
letter in uppercase is the right thing. Ideally there should be only
[Description] in the tree at this point.
> >> + *
> >> +
> >> + /* Create squashfs without any comporession.
> >> + * This allows reasoning about block sizes
> >> + */
> >> + TST_EXP_PASS(tst_system(
> >> + "mksquashfs data image.raw -noI -noD -noX -noF >/dev/null 2>&1"
> > I guess the existing API functions to create an image will not work with
> > squashfs?
> Honestly I don't know what they are... If it is .format_device stuff,
> then no, this cannot be used
> for squashfs, because the data has to be prepared, before the filesystem
> can be created.
Indeed, there is not much to be done here.
> ???????? SAFE_MKDIR("mnt", 0777);
> -?????? TST_EXP_PASS(tst_system("mount -tsquashfs -oloop image.raw mnt"));
> +?????? TST_EXP_PASS(mount(tst_device->dev, "mnt", "squashfs", 0, NULL));
I do not think that it matters that much who allocates the device, if
it's the test library or the kernel code. I guess that in both cases it
just picks up the first free device anyways.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2021-07-14 8:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 5:52 [LTP] [PATCH v2] squashfs: Add regression test for sanity check bug Joerg Vehlow
2021-07-14 6:53 ` Richard Palethorpe
2021-07-14 7:40 ` Joerg Vehlow
2021-07-14 8:40 ` Cyril Hrubis [this message]
2021-07-14 8:35 ` Cyril Hrubis
2021-07-14 9:26 ` Joerg Vehlow
2021-07-14 9:26 ` Cyril Hrubis
2021-07-14 9:58 ` Joerg Vehlow
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=YO6i4QqnULLpsoZv@yuki \
--to=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