All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: P J P <ppandit@redhat.com>,
	libvir-list@redhat.com, Gerd Hoffmann <kraxel@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/3] cirrus: mark as deprecated
Date: Fri, 26 Oct 2018 15:14:58 +0100	[thread overview]
Message-ID: <20181026141458.GA493@redhat.com> (raw)
In-Reply-To: <4e377111-8b95-c65a-e456-a7a8a4580ecb@redhat.com>

On Fri, Oct 26, 2018 at 12:03:35PM +0200, Paolo Bonzini wrote:
> On 26/10/2018 11:59, Daniel P. Berrangé wrote:
> > I should also say that QEMU as an upstream project has multiple goals.
> > Running KVM guests with modern PV hardware is only one of them, albeit
> > a widely used one. Being able to run old legacy OS with old hardware,
> > and running arbitrary embedded boards/devices with emulation are both
> > use cases that QEMU project aims to address. To eliminate all the old
> > "crufty" device emulation in name of improving security for KVM, would
> > be to eliminate core use cases of the project. THis is why we're trying
> > to persue the direction of making it easier for vendors to disable
> > features and devices they don't wish to support & thus limit their
> > downstream CVE exposure.
> 
> Indeed.  If we had to deprecate a feature just because it had an
> off-by-one bug, no C program would grow beyond 1000 lines of code...

One thing we should do, however, is to make it clear which of the
device models we consider secure, and which we consider only usable
in a friendly guest environment, as we have very different code
maintainership & quality standards for different parts of QEMU.

Essentially virtio devices, and then only a handful of the emulated
devices are things we consider suitable for usage in secure envs.
Likewise for machine types probably.


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 :|

  reply	other threads:[~2018-10-26 14:15 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-25  8:52 [Qemu-devel] [PATCH 0/3] RfC: add support for deprecated devices Gerd Hoffmann
2018-10-25  8:52 ` [Qemu-devel] [PATCH 1/3] qdev: add deprecation_reason to DeviceClass Gerd Hoffmann
2018-10-25 10:50   ` P J P
2018-10-25 11:12   ` Philippe Mathieu-Daudé
2018-10-29  9:19     ` Gerd Hoffmann
2018-10-25  8:52 ` [Qemu-devel] [PATCH 2/3] adlib: mark as insecure and deprecated Gerd Hoffmann
2018-10-25 10:56   ` P J P
2018-10-25 20:40     ` [Qemu-devel] [libvirt] " Daniel P. Berrangé
2018-10-26  7:08       ` P J P
2018-10-26  9:54         ` Daniel P. Berrangé
2018-10-26 12:35           ` P J P
2018-10-25 11:15   ` [Qemu-devel] " Philippe Mathieu-Daudé
2018-10-25 20:27   ` Thomas Huth
2018-10-26  8:48   ` Paolo Bonzini
2018-10-26  9:34     ` P J P
2018-10-26 10:01       ` Paolo Bonzini
2018-10-26 11:53         ` P J P
2018-10-29  9:05           ` Gerd Hoffmann
2018-10-25  8:52 ` [Qemu-devel] [PATCH 3/3] cirrus: mark as deprecated Gerd Hoffmann
2018-10-25 10:59   ` P J P
2018-10-25 11:17   ` Philippe Mathieu-Daudé
2018-10-25 20:28   ` Thomas Huth
2018-10-25 20:37   ` Daniel P. Berrangé
2018-10-26  7:03     ` P J P
2018-10-26  9:42       ` Daniel P. Berrangé
2018-10-26  9:59         ` Daniel P. Berrangé
2018-10-26 10:03           ` Paolo Bonzini
2018-10-26 14:14             ` Daniel P. Berrangé [this message]
2018-10-26 18:56               ` P J P
2018-10-26 10:40         ` Dr. David Alan Gilbert
2018-10-26 13:25         ` [Qemu-devel] [libvirt] " Christian Borntraeger
2018-10-26  8:48     ` Cole Robinson
2018-10-26  9:43       ` Daniel P. Berrangé
2018-10-29  9:12     ` [Qemu-devel] " Gerd Hoffmann
2018-10-30 18:00       ` Daniel P. Berrangé

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=20181026141458.GA493@redhat.com \
    --to=berrange@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=libvir-list@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=ppandit@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 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.