From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:57535) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tl14q-0003FE-4N for qemu-devel@nongnu.org; Tue, 18 Dec 2012 12:35:37 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Tl14o-0001Bt-F0 for qemu-devel@nongnu.org; Tue, 18 Dec 2012 12:35:36 -0500 Received: from 70-88-178-169-atlanta.hfc.comcastbusiness.net ([70.88.178.169]:44002 helo=mail.inetric.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tl14o-0001BM-2j for qemu-devel@nongnu.org; Tue, 18 Dec 2012 12:35:34 -0500 Date: Tue, 18 Dec 2012 12:34:22 -0500 From: Michael Contreras Message-ID: <20121218173422.GA16762@inetric.com> References: <20121205121317.GC6887@stefanha-thinkpad.redhat.com> <20121205183130.GA26052@inetric.com> <20121218134420.GC6697@stefanha-thinkpad.redhat.com> <50D097D6.1020008@msgid.tls.msk.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [PATCH] e1000: Discard oversized packets based on SBP|LPE List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: Stefan Hajnoczi , michael@inetric.com, kangli@virtualdevicetech.com, Michael Tokarev , qemu-devel , Anthony Liguori , Andreas Faerber On Tue, Dec 18, 2012 at 05:49:16PM +0100, Stefan Hajnoczi wrote: > On Tue, Dec 18, 2012 at 5:20 PM, Michael Tokarev 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 > >>> --- > >>> 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