From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: Deepanshu Kartikey <kartikey406@gmail.com>,
airlied@redhat.com, kraxel@redhat.com,
gurchetansingh@chromium.org, olvaffe@gmail.com,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, simona@ffwll.ch, sumit.semwal@linaro.org,
christian.koenig@amd.com
Cc: dri-devel@lists.freedesktop.org, virtualization@lists.linux.dev,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linaro-mm-sig@lists.linaro.org,
syzbot+72bd3dd3a5d5f39a0271@syzkaller.appspotmail.com,
stable@vger.kernel.org
Subject: Re: [PATCH v3] drm/virtio: use uninterruptible resv lock for plane updates
Date: Sun, 17 May 2026 19:14:32 +0300 [thread overview]
Message-ID: <afec1199-4889-4d35-964c-4432ec792fa3@collabora.com> (raw)
In-Reply-To: <20260515084030.21986-1-kartikey406@gmail.com>
On 5/15/26 11:40, Deepanshu Kartikey wrote:
> +int virtio_gpu_array_lock_resv_uninterruptible(struct virtio_gpu_object_array *objs)
> +{
> + unsigned int i;
> + int ret = 0;
> +
> + if (objs->nents == 1) {
> + dma_resv_lock(objs->objs[0]->resv, NULL);
> + } else {
> + ret = drm_gem_lock_reservations(objs->objs, objs->nents,
> + &objs->ticket);
drm_gem_lock_reservations() is interruptible. Given that only one BO
needs to be locked for the fix, make it
virtio_gpu_lock_one_resv_uninterruptible() and fail with -EINVAL if
objs->nents > 1
--
Best regards,
Dmitry
next prev parent reply other threads:[~2026-05-17 16:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 8:40 [PATCH v3] drm/virtio: use uninterruptible resv lock for plane updates Deepanshu Kartikey
2026-05-17 16:14 ` Dmitry Osipenko [this message]
2026-05-19 8:24 ` [Linaro-mm-sig] " Deepanshu Kartikey
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=afec1199-4889-4d35-964c-4432ec792fa3@collabora.com \
--to=dmitry.osipenko@collabora.com \
--cc=airlied@redhat.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gurchetansingh@chromium.org \
--cc=kartikey406@gmail.com \
--cc=kraxel@redhat.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=olvaffe@gmail.com \
--cc=simona@ffwll.ch \
--cc=stable@vger.kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=syzbot+72bd3dd3a5d5f39a0271@syzkaller.appspotmail.com \
--cc=tzimmermann@suse.de \
--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