From: P J P <ppandit@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Igor Mammedov <imammedo@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
public@hansmi.ch, QEMU Developers <qemu-devel@nongnu.org>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] i2c: pm_smbus: check smb_index before block transfer write
Date: Thu, 6 Dec 2018 17:34:44 +0530 (IST) [thread overview]
Message-ID: <nycvar.YSQ.7.76.1812061734090.2113@xnncv> (raw)
In-Reply-To: <CAFEAcA9N9sqi4fSp1epPdCV7PkqXpZK4kyoHErvfx3hwcN3kag@mail.gmail.com>
+-- On Thu, 6 Dec 2018, Peter Maydell wrote --+
| > > Do we need patch v2, or it can be done while merging it?
| >
| > I can add in the Fixes line when I apply the patch to master.
|
| Oh, I think we should also add to the commit message something
| along the lines of:
|
| "Note that this bug is exploitable by a guest to escape
| from the virtual machine. However the commit which
| introduced the bug was only made after the 3.0 release,
| and so it is not present in any released QEMU version."
|
| to clarify that this is a serious bug but also that it's
| not one that will be affecting anybody's production systems.
Okay, preparing patch v2...
--
Prasad J Pandit / Red Hat Product Security Team
47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F
next prev parent reply other threads:[~2018-12-06 12:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 8:48 [Qemu-devel] [PATCH] i2c: pm_smbus: check smb_index before block transfer write P J P
2018-12-06 9:02 ` li qiang
2018-12-06 10:14 ` li qiang
2018-12-06 10:16 ` Peter Maydell
2018-12-06 10:34 ` li qiang
2018-12-06 10:46 ` Peter Maydell
2018-12-06 10:59 ` Li Qiang
2018-12-06 11:05 ` Peter Maydell
2018-12-06 11:12 ` Li Qiang
2018-12-06 11:13 ` Peter Maydell
2018-12-06 9:48 ` Igor Mammedov
2018-12-06 10:14 ` Peter Maydell
2018-12-06 9:58 ` Igor Mammedov
2018-12-06 11:08 ` P J P
2018-12-06 11:19 ` Peter Maydell
2018-12-06 11:22 ` Peter Maydell
2018-12-06 12:04 ` P J P [this message]
2018-12-06 12:22 ` P J P
2018-12-06 11:33 ` li qiang
2018-12-06 11:35 ` Michael Hanselmann
2018-12-06 20:16 ` Michael Hanselmann
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=nycvar.YSQ.7.76.1812061734090.2113@xnncv \
--to=ppandit@redhat.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=public@hansmi.ch \
--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).