From: Richard Palethorpe <rpalethorpe@suse.de>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2] squashfs: Add regression test for sanity check bug
Date: Wed, 14 Jul 2021 07:53:31 +0100 [thread overview]
Message-ID: <871r81pes4.fsf@suse.de> (raw)
In-Reply-To: <20210714055253.1668374-1-lkml@jv-coder.de>
Hello Joerg,
Joerg Vehlow <lkml@jv-coder.de> writes:
> From: Joerg Vehlow <joerg.vehlow@aox-tech.de>
>
> Adds a regression test for the fixes
> c1b2028315 ("squashfs: fix inode lookup sanity checks")
> and
> 8b44ca2b62 ("squashfs: fix xattr id and id lookup sanity checks")
>
> Signed-off-by: Joerg Vehlow <joerg.vehlow@aox-tech.de>
> ---
>
> Changes to v1:
> - Implement whole test in c
> - Fixed whitespaces...
>
> runtest/fs | 2 +
> testcases/kernel/fs/squashfs/.gitignore | 1 +
> testcases/kernel/fs/squashfs/Makefile | 9 ++
> .../kernel/fs/squashfs/squashfs_regression.c | 99 +++++++++++++++++++
> 4 files changed, 111 insertions(+)
> create mode 100644 testcases/kernel/fs/squashfs/.gitignore
> create mode 100644 testcases/kernel/fs/squashfs/Makefile
> create mode 100644 testcases/kernel/fs/squashfs/squashfs_regression.c
>
> diff --git a/runtest/fs b/runtest/fs
> index 17b1415eb..2091b00f8 100644
> --- a/runtest/fs
> +++ b/runtest/fs
> @@ -85,3 +85,5 @@ fs_fill fs_fill
>
> binfmt_misc01 binfmt_misc01.sh
> binfmt_misc02 binfmt_misc02.sh
> +
> +squashfs_regression squashfs_regression
> diff --git a/testcases/kernel/fs/squashfs/.gitignore b/testcases/kernel/fs/squashfs/.gitignore
> new file mode 100644
> index 000000000..45c908fff
> --- /dev/null
> +++ b/testcases/kernel/fs/squashfs/.gitignore
> @@ -0,0 +1 @@
> +squashfs_regression
> diff --git a/testcases/kernel/fs/squashfs/Makefile b/testcases/kernel/fs/squashfs/Makefile
> new file mode 100644
> index 000000000..67021139c
> --- /dev/null
> +++ b/testcases/kernel/fs/squashfs/Makefile
> @@ -0,0 +1,9 @@
> +# SPDX-License-Identifier: GPL-2.0-or-later
> +# Copyright (C) 2009, Cisco Systems Inc.
> +# Ngie Cooper, July 2009
> +
> +top_srcdir ?= ../../../..
> +
> +include $(top_srcdir)/include/mk/testcases.mk
> +
> +include $(top_srcdir)/include/mk/generic_leaf_target.mk
> diff --git a/testcases/kernel/fs/squashfs/squashfs_regression.c b/testcases/kernel/fs/squashfs/squashfs_regression.c
> new file mode 100644
> index 000000000..23f681367
> --- /dev/null
> +++ b/testcases/kernel/fs/squashfs/squashfs_regression.c
> @@ -0,0 +1,99 @@
> +// SPDX-License-Identifier: GPL-2.0-or-later
> +/*
> + * Copyright (c) 2021 Joerg Vehlow <joerg.vehlow@aox-tech.de>
> + */
> +
> +/*\
> + * [DESCRIPTION]
I think it is [Description] now.
> + *
> + * Kernel commits
> + *
> + * - f37aa4c7366 (squashfs: add more sanity checks in id lookup)
> + * - eabac19e40c (squashfs: add more sanity checks in inode lookup)
> + * - 506220d2ba2 (squashfs: add more sanity checks in xattr id lookup)
> + *
> + * added some sanity checks, that verify the size of
> + * inode lookup, id (uid/gid) and xattr blocks in the squashfs,
> + * but broke mounting filesystems with completely filled blocks.
> + * A block has a max size of 8192.
> + * An inode lookup entry has an uncompressed size of 8 bytes,
> + * an id block 4 bytes and an xattr block 16 bytes.
> + *
> + *
> + * To fill up at least one block for each of the three tables,
> + * 2048 files with unique uid/gid and xattr are created.
> + *
> + *
> + * The bugs are fixed in kernel commits
> + *
> + * - c1b2028315c (squashfs: fix inode lookup sanity checks)
> + * - 8b44ca2b634 (squashfs: fix xattr id and id lookup sanity checks)
> + */
> +
> +#include <stdio.h>
> +#include <sys/mount.h>
> +
> +#include "tst_test.h"
> +#include "tst_safe_macros.h"
> +
> +static void cleanup(void)
> +{
> + umount("mnt");
> +}
> +
> +static void run(void)
> +{
> + int i;
> +
> + tst_res(TINFO, "Test squashfs sanity check regressions");
> +
> + SAFE_MKDIR("data", 0777);
> +
> + for (i = 0; i < 2048; ++i) {
> + int fd;
> + char name[20];
> +
> + sprintf(name, "data/%d", i);
> + fd = SAFE_OPEN(name, O_CREAT | O_EXCL, 0666);
> + SAFE_FCHOWN(fd, i, i);
> +
> + /* This must be either "security", "user" or "trusted" namespace,
> + * because squashfs cannot store other namespaces.
> + * Since the files are most likely created on a tmpfs,
> + * "user" namespace is not possible, because it is not allowed.
> + */
> + SAFE_FSETXATTR(fd, "security.x", &i, sizeof(i), 0);
> + close(fd);
> + }
> +
> + /* 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?
At any rate, mksquashfs should be added to .needs_cmds.
> + ), "Create squashfs");
> +
> + SAFE_MKDIR("mnt", 0777);
> + TST_EXP_PASS(tst_system("mount -tsquashfs -oloop image.raw
> mnt"));
Also why not use safe_mount? I think we have some infra to find a spare
loop device (.needs_device).
> +
> + SAFE_UMOUNT("mnt");
> +
> + tst_res(TPASS, "Test passed");
> +}
> +
> +static struct tst_test test = {
> + .test_all = run,
> + .cleanup = cleanup,
> + .needs_root = 1,
> + .needs_drivers = (const char *const []) {
> + "squashfs",
> + "loop",
> + NULL
> + },
> + .tags = (const struct tst_tag[]) {
> + {"linux-git", "c1b2028315c"},
> + {"linux-git", "8b44ca2b634"},
> + {}
> + },
> + .needs_tmpdir = 1,
> +};
> --
> 2.25.1
--
Thank you,
Richard.
next prev parent reply other threads:[~2021-07-14 6:53 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 [this message]
2021-07-14 7:40 ` Joerg Vehlow
2021-07-14 8:40 ` Cyril Hrubis
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=871r81pes4.fsf@suse.de \
--to=rpalethorpe@suse.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