From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Eduardo Habkost <eduardo@habkost.net>,
Eric Blake <eblake@redhat.com>
Subject: Re: [PATCH v3 3/4] vga/cirrus: mark as not secure
Date: Thu, 6 Jun 2024 15:37:42 +0100 [thread overview]
Message-ID: <ZmHJtrpvbMorfUm1@redhat.com> (raw)
In-Reply-To: <20240606143010.1318226-4-kraxel@redhat.com>
On Thu, Jun 06, 2024 at 04:30:09PM +0200, Gerd Hoffmann wrote:
What's the justification for declaring cirrus to be insecure ?
It is shipped as a driver in RHEL for years, was the default graphics
adapter for most of this time, and bugs in it are considered CVEs
still.
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> ---
> hw/display/cirrus_vga.c | 1 +
> hw/display/cirrus_vga_isa.c | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/hw/display/cirrus_vga.c b/hw/display/cirrus_vga.c
> index 150883a97166..1f4c55b21415 100644
> --- a/hw/display/cirrus_vga.c
> +++ b/hw/display/cirrus_vga.c
> @@ -3007,6 +3007,7 @@ static void cirrus_vga_class_init(ObjectClass *klass, void *data)
> dc->vmsd = &vmstate_pci_cirrus_vga;
> device_class_set_props(dc, pci_vga_cirrus_properties);
> dc->hotpluggable = false;
> + klass->not_secure = true;
> }
>
> static const TypeInfo cirrus_vga_info = {
> diff --git a/hw/display/cirrus_vga_isa.c b/hw/display/cirrus_vga_isa.c
> index 84be51670ed8..535a631b4b09 100644
> --- a/hw/display/cirrus_vga_isa.c
> +++ b/hw/display/cirrus_vga_isa.c
> @@ -85,6 +85,7 @@ static void isa_cirrus_vga_class_init(ObjectClass *klass, void *data)
> dc->realize = isa_cirrus_vga_realizefn;
> device_class_set_props(dc, isa_cirrus_vga_properties);
> set_bit(DEVICE_CATEGORY_DISPLAY, dc->categories);
> + klass->not_secure = true;
> }
>
> static const TypeInfo isa_cirrus_vga_info = {
> --
> 2.45.2
>
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2024-06-06 14:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 14:30 [PATCH v3 0/4] allow to deprecate objects and devices Gerd Hoffmann
2024-06-06 14:30 ` [PATCH v3 1/4] qom: allow to mark objects as deprecated or not secure Gerd Hoffmann
2024-06-06 14:38 ` Daniel P. Berrangé
2024-06-07 6:24 ` Philippe Mathieu-Daudé
2024-06-12 11:07 ` Markus Armbruster
2024-06-12 11:24 ` Daniel P. Berrangé
2024-06-12 11:44 ` Markus Armbruster
2024-06-06 14:30 ` [PATCH v3 2/4] usb/hub: mark as deprecated Gerd Hoffmann
2024-06-06 14:41 ` Daniel P. Berrangé
2024-06-12 15:52 ` Alex Bennée
2024-06-13 8:31 ` Markus Armbruster
2024-06-13 8:34 ` Daniel P. Berrangé
2024-06-13 10:38 ` Markus Armbruster
2024-06-13 10:48 ` Daniel P. Berrangé
2024-06-13 14:49 ` Alex Bennée
2024-06-14 7:03 ` Gerd Hoffmann
2024-06-13 8:44 ` Daniel P. Berrangé
2024-06-14 8:40 ` Gerd Hoffmann
2024-06-06 14:30 ` [PATCH v3 3/4] vga/cirrus: mark as not secure Gerd Hoffmann
2024-06-06 14:37 ` Daniel P. Berrangé [this message]
2024-06-06 14:30 ` [PATCH v3 4/4] qdev: add device policy [RfC] Gerd Hoffmann
2024-06-06 14:49 ` Peter Maydell
2024-06-12 8:30 ` Markus Armbruster
2024-06-12 11:40 ` [PATCH v3 0/4] allow to deprecate objects and devices Markus Armbruster
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=ZmHJtrpvbMorfUm1@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=eduardo@habkost.net \
--cc=kraxel@redhat.com \
--cc=pbonzini@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).