From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, Hanna Reitz <hreitz@redhat.com>
Subject: Re: [PATCH] iotests/108: avoid leaking FUSE mount
Date: Mon, 20 Jul 2026 13:54:02 -0400 [thread overview]
Message-ID: <20260720175402.GA67869@fedora> (raw)
In-Reply-To: <20260611125438.194479-1-stefanha@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 886 bytes --]
On Thu, Jun 11, 2026 at 08:54:38AM -0400, Stefan Hajnoczi wrote:
> The QEMU s390x CI gitlab-runner recently broke because qemu-iotests 108
> FUSE mount leaked and prevented the setup of the gitlab-runner
> environment:
>
> chmod: cannot access '/home/gitlab-runner/builds/P3MFS4LUf/0/qemu-project/qemu/build/scratch/qcow2-file-108/fuse-export': Transport endpoint is not connected
>
> https://gitlab.com/qemu-project/qemu/-/jobs/14796143507#L11
>
> Always umount the FUSE export when cleaning up to prevent the leak.
>
> Closes: https://gitlab.com/qemu-project/qemu/-/work_items/3541
> Cc: Hanna Czenczek <hreitz@redhat.com>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
> tests/qemu-iotests/108 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Thanks, applied to my block tree:
https://gitlab.com/stefanha/qemu/commits/block
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-07-20 17:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 12:54 [PATCH] iotests/108: avoid leaking FUSE mount Stefan Hajnoczi
2026-06-11 13:03 ` Daniel P. Berrangé
2026-07-20 17:54 ` Stefan Hajnoczi [this message]
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=20260720175402.GA67869@fedora \
--to=stefanha@redhat.com \
--cc=hreitz@redhat.com \
--cc=kwolf@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox