From: Michael Contreras <michael@inetric.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
michael@inetric.com, kangli@virtualdevicetech.com,
Michael Tokarev <mjt@tls.msk.ru>,
qemu-devel <qemu-devel@nongnu.org>,
Anthony Liguori <anthony@codemonkey.ws>,
Andreas Faerber <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH] e1000: Discard oversized packets based on SBP|LPE
Date: Tue, 18 Dec 2012 12:34:22 -0500 [thread overview]
Message-ID: <20121218173422.GA16762@inetric.com> (raw)
In-Reply-To: <CAJSP0QXsEBX4vzs0kdtAmgi71ksn+n+44Sq9NSUYm++u37fC9w@mail.gmail.com>
On Tue, Dec 18, 2012 at 05:49:16PM +0100, Stefan Hajnoczi wrote:
> On Tue, Dec 18, 2012 at 5:20 PM, Michael Tokarev <mjt@tls.msk.ru> wrote:
> > On 18.12.2012 17:44, Stefan Hajnoczi wrote:
> >> On Wed, Dec 05, 2012 at 01:31:30PM -0500, Michael Contreras wrote:
> >>> Discard packets longer than 16384 when !SBP to match the hardware behavior.
> >>>
> >>> Signed-off-by: Michael Contreras <michael@inetric.com>
> >>> ---
> >>> hw/e1000.c | 7 +++++--
> >>> 1 file changed, 5 insertions(+), 2 deletions(-)
> >
> > It looks like another very good candidate for -stable (up to quite some
> > releases of qemu ago), together with the previous similar patch.
>
> Yes, it's good for -stable.
>
> Stefan
Thanks guys. Any update on the CVE number? Seems the KVM qemu git tree
still has this vulnerability. Xen has the fix in their qemu unstable
git mirror, but hasn't applied it yet either.
Michael
next prev parent reply other threads:[~2012-12-18 17:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20121205121317.GC6887@stefanha-thinkpad.redhat.com>
2012-12-05 18:31 ` [Qemu-devel] [PATCH] e1000: Discard oversized packets based on SBP|LPE Michael Contreras
2012-12-18 13:44 ` Stefan Hajnoczi
2012-12-18 16:20 ` Michael Tokarev
2012-12-18 16:49 ` Stefan Hajnoczi
2012-12-18 17:34 ` Michael Contreras [this message]
2012-12-19 11:42 ` Stefan Hajnoczi
2012-12-30 8:29 ` Michael Tokarev
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=20121218173422.GA16762@inetric.com \
--to=michael@inetric.com \
--cc=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=kangli@virtualdevicetech.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefanha@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 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).