From: Eric Farman <farman@linux.ibm.com>
To: Kevin Wolf <kwolf@redhat.com>, Hanna Reitz <hreitz@redhat.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org,
Matthew Rosato <mjrosato@linux.ibm.com>,
Eric Farman <farman@linux.ibm.com>
Subject: [PATCH v1 1/3] iotests/108: skip test if cannot access /dev/fuse
Date: Sat, 25 Jul 2026 14:56:49 +0200 [thread overview]
Message-ID: <20260725125651.3896151-2-farman@linux.ibm.com> (raw)
In-Reply-To: <20260725125651.3896151-1-farman@linux.ibm.com>
This test might fail if the user is not root (or sudo'd):
fusermount3: failed to open .../scratch/qcow2-file-108/fuse-export: Permission denied
A check exists to try to cover for this, but there are
two potential error messages that signal this case
(per the comment block associated with the check) and
only a skip for one of them.
Add a check for the other potential error message.
Fixes: 9ffd6d646d ("iotests/108: Test new refcount rebuild algorithm")
Signed-off-by: Eric Farman <farman@linux.ibm.com>
---
tests/qemu-iotests/108 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/qemu-iotests/108 b/tests/qemu-iotests/108
index bf808b3512..136007ceaf 100755
--- a/tests/qemu-iotests/108
+++ b/tests/qemu-iotests/108
@@ -69,7 +69,7 @@ else
# or "Invalid parameter 'fuse'", depending on whether there is
# FUSE support or not.
error=$($QSD --export fuse 2>&1)
- if [[ $error = *"'fuse'"* ]]; then
+ if [[ $error = *"'fuse'"* || $error = *"'id'"* ]]; then
_notrun 'Passwordless sudo for losetup or FUSE support required, but' \
'neither is available'
fi
--
2.53.0
next prev parent reply other threads:[~2026-07-25 12:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-25 12:56 [PATCH v1 0/3] io_tests fuse fixes Eric Farman
2026-07-25 12:56 ` Eric Farman [this message]
2026-07-25 12:56 ` [PATCH v1 2/3] iotests/file-io-error: complete permission denied check Eric Farman
2026-07-25 12:56 ` [PATCH v1 3/3] iotests/fuse-mmap-shared: " Eric Farman
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=20260725125651.3896151-2-farman@linux.ibm.com \
--to=farman@linux.ibm.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mjrosato@linux.ibm.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.