From: Emil Velikov <emil.velikov@collabora.com>
To: Dmitry Osipenko <dmitry.osipenko@collabora.com>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Gurchetan Singh <gurchetansingh@chromium.org>,
Gerd Hoffmann <kraxel@redhat.com>,
Ryan Neph <ryanneph@chromium.org>,
David Airlie <airlied@redhat.com>,
Javier Martinez Canillas <javierm@redhat.com>,
kernel@collabora.com, virtualization@lists.linux-foundation.org
Subject: Re: [PATCH v2] drm/virtio: Fix handling CONFIG_DRM_VIRTIO_GPU_KMS option
Date: Mon, 6 Mar 2023 15:02:04 +0000 [thread overview]
Message-ID: <ZAYAbIXlLLkNCB6f@arch-x395> (raw)
In-Reply-To: <20230306143234.1561759-1-dmitry.osipenko@collabora.com>
On 2023/03/06, Dmitry Osipenko wrote:
> VirtIO-GPU got a new config option for disabling KMS. There were two
> problems left unnoticed during review when the new option was added:
>
> 1. The IS_ENABLED(CONFIG_DRM_VIRTIO_GPU_KMS) check in the code was
> inverted, hence KMS was disabled when it should be enabled and vice versa.
>
> 2. The disabled KMS crashed kernel with a NULL dereference in
> drm_kms_helper_hotplug_event(), which shall not be invoked with a
> disabled KMS.
>
> Fix the inverted config option check in the code and skip handling the
> VIRTIO_GPU_EVENT_DISPLAY sent by host when KMS is disabled in guest to fix
> the crash.
>
> Fixes: 72122c69d717 ("drm/virtio: Add option to disable KMS support")
> Signed-off-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
> ---
>
> Changelog:
>
> v2: - Moved the "has_edid" under the "num_scanouts" condition, like was
> suggested by Gerd Hoffmann.
>
Hi Dmitry, I think there's more than one piece like that in the driver.
> drivers/gpu/drm/virtio/virtgpu_kms.c | 14 ++++++++------
> 1 file changed, 8 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/virtio/virtgpu_kms.c b/drivers/gpu/drm/virtio/virtgpu_kms.c
> index 874ad6c2621a..15f2519988e7 100644
> --- a/drivers/gpu/drm/virtio/virtgpu_kms.c
> +++ b/drivers/gpu/drm/virtio/virtgpu_kms.c
> @@ -43,11 +43,13 @@ static void virtio_gpu_config_changed_work_func(struct work_struct *work)
> virtio_cread_le(vgdev->vdev, struct virtio_gpu_config,
> events_read, &events_read);
> if (events_read & VIRTIO_GPU_EVENT_DISPLAY) {
> - if (vgdev->has_edid)
> - virtio_gpu_cmd_get_edids(vgdev);
> - virtio_gpu_cmd_get_display_info(vgdev);
> - virtio_gpu_notify(vgdev);
> - drm_helper_hpd_irq_event(vgdev->ddev);
> + if (vgdev->num_scanouts) {
> + if (vgdev->has_edid)
> + virtio_gpu_cmd_get_edids(vgdev);
Worth doing the same thing in virtio_gpu_init()? Aka move the has_edid
&& get_edids within the num_scanouts if block.
HTH
Emil
WARNING: multiple messages have this Message-ID (diff)
From: Emil Velikov <emil.velikov@collabora.com>
To: Dmitry Osipenko <dmitry.osipenko@collabora.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
Rob Clark <robdclark@gmail.com>,
Gurchetan Singh <gurchetansingh@chromium.org>,
Chia-I Wu <olvaffe@gmail.com>, Ryan Neph <ryanneph@chromium.org>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Javier Martinez Canillas <javierm@redhat.com>,
David Airlie <airlied@redhat.com>,
kernel@collabora.com, virtualization@lists.linux-foundation.org
Subject: Re: [PATCH v2] drm/virtio: Fix handling CONFIG_DRM_VIRTIO_GPU_KMS option
Date: Mon, 6 Mar 2023 15:02:04 +0000 [thread overview]
Message-ID: <ZAYAbIXlLLkNCB6f@arch-x395> (raw)
In-Reply-To: <20230306143234.1561759-1-dmitry.osipenko@collabora.com>
On 2023/03/06, Dmitry Osipenko wrote:
> VirtIO-GPU got a new config option for disabling KMS. There were two
> problems left unnoticed during review when the new option was added:
>
> 1. The IS_ENABLED(CONFIG_DRM_VIRTIO_GPU_KMS) check in the code was
> inverted, hence KMS was disabled when it should be enabled and vice versa.
>
> 2. The disabled KMS crashed kernel with a NULL dereference in
> drm_kms_helper_hotplug_event(), which shall not be invoked with a
> disabled KMS.
>
> Fix the inverted config option check in the code and skip handling the
> VIRTIO_GPU_EVENT_DISPLAY sent by host when KMS is disabled in guest to fix
> the crash.
>
> Fixes: 72122c69d717 ("drm/virtio: Add option to disable KMS support")
> Signed-off-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
> ---
>
> Changelog:
>
> v2: - Moved the "has_edid" under the "num_scanouts" condition, like was
> suggested by Gerd Hoffmann.
>
Hi Dmitry, I think there's more than one piece like that in the driver.
> drivers/gpu/drm/virtio/virtgpu_kms.c | 14 ++++++++------
> 1 file changed, 8 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/virtio/virtgpu_kms.c b/drivers/gpu/drm/virtio/virtgpu_kms.c
> index 874ad6c2621a..15f2519988e7 100644
> --- a/drivers/gpu/drm/virtio/virtgpu_kms.c
> +++ b/drivers/gpu/drm/virtio/virtgpu_kms.c
> @@ -43,11 +43,13 @@ static void virtio_gpu_config_changed_work_func(struct work_struct *work)
> virtio_cread_le(vgdev->vdev, struct virtio_gpu_config,
> events_read, &events_read);
> if (events_read & VIRTIO_GPU_EVENT_DISPLAY) {
> - if (vgdev->has_edid)
> - virtio_gpu_cmd_get_edids(vgdev);
> - virtio_gpu_cmd_get_display_info(vgdev);
> - virtio_gpu_notify(vgdev);
> - drm_helper_hpd_irq_event(vgdev->ddev);
> + if (vgdev->num_scanouts) {
> + if (vgdev->has_edid)
> + virtio_gpu_cmd_get_edids(vgdev);
Worth doing the same thing in virtio_gpu_init()? Aka move the has_edid
&& get_edids within the num_scanouts if block.
HTH
Emil
next prev parent reply other threads:[~2023-03-06 15:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 14:32 [PATCH v2] drm/virtio: Fix handling CONFIG_DRM_VIRTIO_GPU_KMS option Dmitry Osipenko
2023-03-06 14:32 ` Dmitry Osipenko
2023-03-06 14:46 ` Gerd Hoffmann
2023-03-06 14:46 ` Gerd Hoffmann
2023-03-06 14:46 ` Gerd Hoffmann
2023-03-06 15:02 ` Emil Velikov [this message]
2023-03-06 15:02 ` Emil Velikov
2023-03-06 15:55 ` Dmitry Osipenko
2023-03-06 15:55 ` 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=ZAYAbIXlLLkNCB6f@arch-x395 \
--to=emil.velikov@collabora.com \
--cc=airlied@redhat.com \
--cc=dmitry.osipenko@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gurchetansingh@chromium.org \
--cc=javierm@redhat.com \
--cc=kernel@collabora.com \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ryanneph@chromium.org \
--cc=virtualization@lists.linux-foundation.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.