From: Markus Armbruster <armbru@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Prasad J Pandit" <pjp@fedoraproject.org>,
"patches@linaro.org" <patches@linaro.org>,
"Jan Kiszka" <jan.kiszka@siemens.com>,
"Jason Wang" <jasowang@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
liqsub1 <liqsub1@163.com>,
"Samuel Thibault" <samuel.thibault@ens-lyon.org>,
qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH for-3.0] slirp: Correct size check in m_inc()
Date: Tue, 07 Aug 2018 17:47:48 +0200 [thread overview]
Message-ID: <87bmae41qz.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <CAFEAcA99ybqO=f+s2_S8ypU6-Hy5iRGwviFceaN8Trne+MA8jw@mail.gmail.com> (Peter Maydell's message of "Tue, 7 Aug 2018 14:47:20 +0100")
Peter Maydell <peter.maydell@linaro.org> writes:
> On 7 August 2018 at 14:09, Daniel P. Berrangé <berrange@redhat.com> wrote:
>> On Tue, Aug 07, 2018 at 03:07:07PM +0200, Thomas Huth wrote:
>>> But 864036e251f54c9 was never part of an official QEMU release, was it?
>>> Or did it go into a stable release already? If not, I think you simply
>>> need both patches to fix the CVE instead.
>>
>> Ah possibly - I didn't look at where 864036e251f54c9 was actually
>> release or not. If its onyl git master, then yeah, we can use the
>> same CVE we already have.
>
> Yeah, we haven't released anything with 864036e251f54c9 in it yet.
> (In particular we did not flag it up for stable and so it is not
> in 2.12.1...)
Pointing out the obvious: this is a second opportunity to flag the CVE
fix for stable.
next prev parent reply other threads:[~2018-08-07 15:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 11:45 [Qemu-devel] [PATCH for-3.0] slirp: Correct size check in m_inc() Peter Maydell
2018-08-07 11:54 ` Samuel Thibault
2018-08-07 12:52 ` Dr. David Alan Gilbert
2018-08-07 12:58 ` Daniel P. Berrangé
2018-08-07 13:07 ` Thomas Huth
2018-08-07 13:09 ` Daniel P. Berrangé
2018-08-07 13:47 ` Peter Maydell
2018-08-07 15:47 ` Markus Armbruster [this message]
2018-08-07 15:58 ` Peter Maydell
2018-08-07 13:45 ` Peter Maydell
2018-08-09 11:12 ` Dr. David Alan Gilbert
2018-08-09 11:25 ` Peter Maydell
2018-08-09 11:32 ` Dr. David Alan Gilbert
2018-08-09 21:54 ` Samuel Thibault
2018-08-10 9:02 ` Peter Maydell
2018-08-10 9:08 ` Samuel Thibault
2018-08-10 9:13 ` Peter Maydell
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=87bmae41qz.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=jasowang@redhat.com \
--cc=liqsub1@163.com \
--cc=patches@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=pjp@fedoraproject.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=samuel.thibault@ens-lyon.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.