From: Eryu Guan <guan@eryu.me>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: fstests <fstests@vger.kernel.org>,
Namjae Jeon <namjae.jeon@samsung.com>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH 2/2 V2] fstests: add _require_mknod
Date: Mon, 18 May 2020 00:12:09 +0800 [thread overview]
Message-ID: <20200517161209.GF2704@desktop> (raw)
In-Reply-To: <42fcddeb-7274-bf41-3475-16eae0f78e92@sandeen.net>
On Fri, May 08, 2020 at 09:23:42AM -0500, Eric Sandeen wrote:
> Add a _require_mknod test so that filesystems with no ->mknod
> operation will _notrun instead of fail.
>
> Signed-off-by: Eric Sandeen <sandeen@sandeen.net>
> ---
>
> V2 trim the long line, sorry.
>
> diff --git a/common/rc b/common/rc
> index 2734dbf6..b50a4294 100644
> --- a/common/rc
> +++ b/common/rc
> @@ -4214,6 +4215,13 @@ _require_sysctl()
> sysctl $name &>/dev/null || _notrun "$name sysctl unavailable"
> }
>
> +_require_mknod()
> +{
> + mknod $TEST_DIR/$tmp.null c 1 3 \
$tmp points to /tmp/$$, so this mknod is trying to make node at
$TEST_DIR//tmp/<pid>
which will always fail.
Use $TEST_DIR/$seq.null instead?
And I don't see any callers of this require rule, shouldn't existing
tests that use mknod be updated to require this rule?
Thanks,
Eryu
> + || _notrun "$FSTYP does not support mknod/mkfifo"
> + rm -f $TEST_DIR/$tmp.null
> +}
> +
> init_rc
>
> ################################################################################
>
next prev parent reply other threads:[~2020-05-17 16:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 22:15 [PATCH 0/2] fstests: 2 more exfat-related fixes Eric Sandeen
2020-05-06 22:16 ` [PATCH 1/2] fstests: update sparse file & negative timestamp tests for exfat Eric Sandeen
2020-05-08 12:05 ` Christoph Hellwig
2020-05-06 22:18 ` [PATCH 2/2] fstests: add _require_mknod Eric Sandeen
2020-05-08 12:05 ` Christoph Hellwig
2020-05-08 14:23 ` [PATCH 2/2 V2] " Eric Sandeen
2020-05-08 15:03 ` Christoph Hellwig
2020-05-17 16:12 ` Eryu Guan [this message]
2020-05-17 21:04 ` Eric Sandeen
2020-05-17 21:13 ` [PATCH 2/2 V3] " Eric Sandeen
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=20200517161209.GF2704@desktop \
--to=guan@eryu.me \
--cc=fstests@vger.kernel.org \
--cc=hch@infradead.org \
--cc=namjae.jeon@samsung.com \
--cc=sandeen@sandeen.net \
/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