From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: Alexandr Sapozhnkiov <alsp705@gmail.com>,
David Airlie <airlied@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Gurchetan Singh <gurchetansingh@chromium.org>,
Chia-I Wu <olvaffe@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Daniel Vetter <daniel@ffwll.ch>,
dri-devel@lists.freedesktop.org, virtualization@lists.linux.dev
Cc: lvc-project@linuxtesting.org
Subject: Re: [PATCH 5.10] gpu/drm/virtio: fix error return in vgdev_output_init()
Date: Wed, 8 Oct 2025 19:47:11 +0300 [thread overview]
Message-ID: <00734e4b-ad39-42bd-b65e-13dcc67a95a0@collabora.com> (raw)
In-Reply-To: <20250922144418.41-1-alsp705@gmail.com>
On 9/22/25 17:44, Alexandr Sapozhnkiov wrote:
> From: Alexandr Sapozhnikov <alsp705@gmail.com>
>
> Return value of function drm_crtc_init_with_planes(),
> called at virtgpu_display.c:276, is not checked,
> but it is usually checked for this function
>
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
> Signed-off-by: Alexandr Sapozhnikov <alsp705@gmail.com>
> ---
> drivers/gpu/drm/virtio/virtgpu_display.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/virtio/virtgpu_display.c b/drivers/gpu/drm/virtio/virtgpu_display.c
> index ad924a8502e9..59b652e8a630 100644
> --- a/drivers/gpu/drm/virtio/virtgpu_display.c
> +++ b/drivers/gpu/drm/virtio/virtgpu_display.c
> @@ -253,6 +253,7 @@ static const struct drm_connector_funcs virtio_gpu_connector_funcs = {
>
> static int vgdev_output_init(struct virtio_gpu_device *vgdev, int index)
> {
> + int ret;
> struct drm_device *dev = vgdev->ddev;
> struct virtio_gpu_output *output = vgdev->outputs + index;
> struct drm_connector *connector = &output->conn;
> @@ -273,8 +274,10 @@ static int vgdev_output_init(struct virtio_gpu_device *vgdev, int index)
> cursor = virtio_gpu_plane_init(vgdev, DRM_PLANE_TYPE_CURSOR, index);
> if (IS_ERR(cursor))
> return PTR_ERR(cursor);
> - drm_crtc_init_with_planes(dev, crtc, primary, cursor,
> + ret = drm_crtc_init_with_planes(dev, crtc, primary, cursor,
> &virtio_gpu_crtc_funcs, NULL);
> + if (ret)
> + return ret;
> drm_crtc_helper_add(crtc, &virtio_gpu_crtc_helper_funcs);
>
> drm_connector_init(dev, connector, &virtio_gpu_connector_funcs,
Patch will need a cosmetic correction for the indentation that I'll
change while applying, thanks.
Reviewed-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
--
Best regards,
Dmitry
next prev parent reply other threads:[~2025-10-08 16:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 14:44 [PATCH 5.10] gpu/drm/virtio: fix error return in vgdev_output_init() Alexandr Sapozhnkiov
2025-10-08 16:47 ` Dmitry Osipenko [this message]
2025-10-09 3:12 ` Dmitry Osipenko
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=00734e4b-ad39-42bd-b65e-13dcc67a95a0@collabora.com \
--to=dmitry.osipenko@collabora.com \
--cc=airlied@redhat.com \
--cc=alsp705@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gurchetansingh@chromium.org \
--cc=kraxel@redhat.com \
--cc=lvc-project@linuxtesting.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=olvaffe@gmail.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;
as well as URLs for NNTP newsgroup(s).