From: Kevin Wolf <kwolf@redhat.com>
To: "Denis V. Lunev" <den@openvz.org>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org,
Hanna Reitz <hreitz@redhat.com>
Subject: Re: [PATCH 2/3] iotests: skip FUSE tests when FUSE is not usable
Date: Tue, 14 Jul 2026 13:19:54 +0200 [thread overview]
Message-ID: <alYbWsd6_58SXYTq@redhat.com> (raw)
In-Reply-To: <20260710161309.1104712-3-den@openvz.org>
Am 10.07.2026 um 18:13 hat Denis V. Lunev geschrieben:
> file-io-error, fuse-allow-other and fuse-mmap-shared skip only when
> FUSE is not compiled in. When FUSE is built in but unusable at run
> time (no /dev/fuse access, fusermount lacking permissions), the
> export fails to mount with "Failed to mount FUSE session to export"
> and the tests report a spurious failure instead of skipping, like
> NBD tests already do for missing NBD support.
>
> Add _notrun_on_no_fuse() to common.rc and use it in the shell tests.
> fuse-mmap-shared is Python, so it gets an equivalent inline check.
>
> Signed-off-by: Denis V. Lunev <den@openvz.org>
> CC: Kevin Wolf <kwolf@redhat.com>
> CC: Hanna Reitz <hreitz@redhat.com>
> ---
> tests/qemu-iotests/common.rc | 14 ++++++++++++++
> tests/qemu-iotests/tests/file-io-error | 4 +---
> tests/qemu-iotests/tests/fuse-allow-other | 2 ++
> tests/qemu-iotests/tests/fuse-mmap-shared | 9 ++++++---
> 4 files changed, 23 insertions(+), 6 deletions(-)
>
> diff --git a/tests/qemu-iotests/common.rc b/tests/qemu-iotests/common.rc
> index 298bc483e0..62a2bc146b 100644
> --- a/tests/qemu-iotests/common.rc
> +++ b/tests/qemu-iotests/common.rc
> @@ -981,6 +981,20 @@ _require_drivers()
> done
> }
>
> +# Skip if FUSE is unusable: not compiled in, or the export failed to
> +# mount. $1 is the failing 'block-export-add' reply.
> +_notrun_on_no_fuse()
I'm not completely happy with the name, though this is not a blocker.
My first thought was to keep the name consistent with the other
functions in common.rc and have something like _require_fuse. On second
thoughts, this is probably confusing because it's different from the
existing _require_* functions in that it takes an error message from the
test case instead of doing its own probing.
So maybe at least remove the double negative? _notrun_on_fuse_error
sounds slightly better to me.
> +{
> + case "$1" in
> + *"Parameter 'type' does not accept value 'fuse'"*)
> + _notrun "No FUSE support"
> + ;;
> + *"Failed to mount FUSE session"*)
> + _notrun "FUSE not usable in this environment"
> + ;;
> + esac
> +}
> +
Adding these checks is a good idea, of course.
Kevin
next prev parent reply other threads:[~2026-07-14 11:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 16:13 [PATCH 0/3] iotests: fix three spurious local failures Denis V. Lunev
2026-07-10 16:13 ` [PATCH 1/3] iotests: run the test pool with the 'fork' start method Denis V. Lunev
2026-07-14 11:08 ` Kevin Wolf
2026-07-10 16:13 ` [PATCH 2/3] iotests: skip FUSE tests when FUSE is not usable Denis V. Lunev
2026-07-14 11:19 ` Kevin Wolf [this message]
2026-07-10 16:13 ` [PATCH 3/3] iotests/migrate-bitmaps-postcopy-test: drop the postcopy timing assertion Denis V. Lunev
2026-07-14 11:28 ` Kevin Wolf
2026-07-14 12:36 ` Vladimir Sementsov-Ogievskiy
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=alYbWsd6_58SXYTq@redhat.com \
--to=kwolf@redhat.com \
--cc=den@openvz.org \
--cc=hreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.