From mboxrd@z Thu Jan 1 00:00:00 1970 From: Neil Horman Subject: Re: [PATCH RFC] r8169: straighten out overlength frame detection Date: Mon, 28 Dec 2009 20:16:09 -0500 Message-ID: <20091229011608.GC7037@localhost.localdomain> References: <20091228194834.GA18422@hmsreliant.think-freely.org> <20091228195053.GB18422@hmsreliant.think-freely.org> <20091228213114.GA24285@zoreil.com> <20091229005152.GV2721@decadent.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: =?iso-8859-1?Q?Fran=E7ois?= romieu , netdev@vger.kernel.org, davem@davemloft.net, eric.dumazet@gmail.com, nhorman@redhat.com To: Ben Hutchings Return-path: Received: from charlotte.tuxdriver.com ([70.61.120.58]:56348 "EHLO smtp.tuxdriver.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750988AbZL2BQS (ORCPT ); Mon, 28 Dec 2009 20:16:18 -0500 Content-Disposition: inline In-Reply-To: <20091229005152.GV2721@decadent.org.uk> Sender: netdev-owner@vger.kernel.org List-ID: On Tue, Dec 29, 2009 at 12:51:52AM +0000, Ben Hutchings wrote: > On Mon, 2009-12-28 at 22:31 +0100, Fran=E7ois romieu wrote: > > (I'm back) > >=20 > > The Mon, Dec 28, 2009 at 02:50:53PM -0500, Neil Horman wrote : > > [...] > > > frames were received on NIC's supported by this driver. This was= mentioned in a > > > security conference recently: > > > http://events.ccc.de/congress/2009/Fahrplan//events/3596.en.html > >=20 > > Is there a paper ? > [...] >=20 > I was present in the session and emailed you and Neil about this > yesterday; did you not get the message? The slides are now linked fr= om > the above page; see pages 74-87. I suggest you ask the speaker if yo= u > need any more details. >=20 > Ben. >=20 I'm sorry, Ben, I don't think I received this note (although I admit I'= ve not been checking to closely over the holidays). I jumped on this after I = got a phone call about it today. I'll make sure to look for your note shortl= y. Neil > --=20 > Ben Hutchings > Always try to do things in chronological order; > it's less confusing that way.