From: sashiko-bot@kernel.org
To: "Changyul Lee" <lcy8047@gmail.com>
Cc: virtualization@lists.linux.dev,
"Michael S. Tsirkin" <mst@redhat.com>,
"Eugenio Perez" <eperezma@redhat.com>
Subject: Re: [PATCH] drm/virtio: Propagate errors from deferred blob mapping
Date: Wed, 28 Oct 2026 22:37:15 +0000 [thread overview]
Message-ID: <sashiko-outbox-188521@kernel.org> (raw)
In-Reply-To: <20261028222500.2575769-1-lcy8047@gmail.com>
> virtio_gpu_vram_map_deferred() ignores errors from
> virtio_gpu_vram_map(). If mapping fails before RESOURCE_MAP_BLOB
> is queued, virtio_gpu_vram_mmap() still waits for a response
> that will never arrive.
>
> This can happen when drm_mm_insert_node() finds no room in
> host_visible_mm. Since no command is sent, map_state remains
> STATE_INITIALIZING. The task then waits indefinitely while holding
> mmap_lock, and SIGKILL cannot terminate it. Any user with render
> node access can trigger this by mmapping a deferred-mapping blob
> larger than the host visible region.
>
> Propagate the error so mmap() returns instead of waiting.
>
> Tested on Linux v7.3 with QEMU (virtio-gpu-gl, blob=true,
> hostmem=256M).
>
> Fixes: 4c26e162947f ("drm/virtio: Extend blob UAPI with deferred-mapping hinting")
> Signed-off-by: Changyul Lee <lcy8047@gmail.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261028222500.2575769-1-lcy8047@gmail.com?part=1
prev parent reply other threads:[~2026-10-28 22:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 22:25 [PATCH] drm/virtio: Propagate errors from deferred blob mapping Changyul Lee
2026-10-28 22:37 ` sashiko-bot [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=sashiko-outbox-188521@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=eperezma@redhat.com \
--cc=lcy8047@gmail.com \
--cc=mst@redhat.com \
--cc=sashiko-reviews@lists.linux.dev \
--cc=virtualization@lists.linux.dev \
/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