All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Laurent Vivier <lvivier@redhat.com>,
	Thomas Huth <thuth@redhat.com>,
	Sebastian Bauer <mail@sebastianbauer.info>,
	Magnus Damm <magnus.damm@gmail.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Zhang Zi Ming <1015138407@qq.com>, qemu-ppc <qemu-ppc@nongnu.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	qemu-stable <qemu-stable@nongnu.org>,
	Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [PATCH-for-5.0 1/2] hw/display/sm501: Avoid heap overflow in sm501_2d_operation()
Date: Sun, 12 Apr 2020 21:57:58 +0100	[thread overview]
Message-ID: <CAFEAcA_U-sxDCSt9DPdNw0PUbjySeWUaNWivezq-6qBFOK3-Eg@mail.gmail.com> (raw)
In-Reply-To: <98306a3a-46c9-cedd-48c2-af065c597640@amsat.org>

On Sun, 12 Apr 2020 at 21:53, Philippe Mathieu-Daudé <f4bug@amsat.org> wrote:
> "VMs using KVM" as security boundary is very clear, thanks.
>
> Note 1: This this doesn't appear on the QEMU security process
> description: https://www.qemu.org/contribute/security-process/

It's part of the list of how to decide whether an issue is
security sensitive:
 "Is QEMU used in conjunction with a hypervisor (as opposed
  to TCG binary translation)?"

We also document it in the user manuals now (a relatively
recent improvement):
 https://www.qemu.org/docs/master/system/security.html#non-virtualization-use-case

> Note 2: If a reported bug is not in security boundary, it should be
> reported as a bug to mainstream QEMU, to give the community a chance to
> fix it.

Yes; bugs are still bugs.

thanks
-- PMM


  reply	other threads:[~2020-04-12 20:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-11  9:14 [PATCH-for-5.0 0/2] hw/display/sm501: Avoid heap overflow in sm501_2d_operation() Philippe Mathieu-Daudé
2020-04-11  9:14 ` [PATCH-for-5.0 1/2] " Philippe Mathieu-Daudé
2020-04-11 18:05   ` BALATON Zoltan
2020-04-11 19:44     ` Philippe Mathieu-Daudé
2020-04-11 21:36       ` Peter Maydell
2020-04-12 20:53         ` Philippe Mathieu-Daudé
2020-04-12 20:57           ` Peter Maydell [this message]
2020-04-12 21:02             ` Philippe Mathieu-Daudé
2020-04-11  9:14 ` [PATCH-for-5.0 2/2] qtest: Test the Drawing Engine of the SM501 companion Philippe Mathieu-Daudé

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=CAFEAcA_U-sxDCSt9DPdNw0PUbjySeWUaNWivezq-6qBFOK3-Eg@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=1015138407@qq.com \
    --cc=aurelien@aurel32.net \
    --cc=f4bug@amsat.org \
    --cc=lvivier@redhat.com \
    --cc=magnus.damm@gmail.com \
    --cc=mail@sebastianbauer.info \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=thuth@redhat.com \
    /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.