From: Neil Horman <nhorman@tuxdriver.com>
To: "Brandeburg, Jesse" <jesse.brandeburg@intel.com>
Cc: "e1000-devel@lists.sourceforge.net"
<e1000-devel@lists.sourceforge.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Allan, Bruce W" <bruce.w.allan@intel.com>,
"Ronciak, John" <john.ronciak@intel.com>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
"davem@davemloft.net" <davem@davemloft.net>
Subject: Re: [PATCH] e1000: enhance frame fragment detection
Date: Tue, 12 Jan 2010 22:33:26 -0500 [thread overview]
Message-ID: <20100113033326.GA1931@localhost.localdomain> (raw)
In-Reply-To: <alpine.WNT.2.00.1001121839130.3168@jbrandeb-desk1.amr.corp.intel.com>
On Tue, Jan 12, 2010 at 06:47:41PM -0800, Brandeburg, Jesse wrote:
> On Tue, 12 Jan 2010, Neil Horman wrote:
> > I'm sorry, it doesn't clear much up, at least not for me. The patch you're
> > referencing above deals only with the jumbo receive path, not the non-jumbo
> > case, which is not written to handle skb chains. The vulnerability targets the
> > latter case specifically. We've seen cases in which an extra data is
> > transferred into a subsequent buffer in the ring in that path. Normally in our
> > reproducing cases, I only saw a 4 byte overrun. Theres a check specifically in
> > the e1000(e) drivers for that case. Unfortunately I never tested other cases,
> > but if someone sets a low mtu (say 1000 bytes), I don't see why the same issue
> > can't manifest as a buffer chain consisting of a 1000 byte skb followed by up to
> > an extra 522 byte skb. such a condition would bypass that check and result in
> > admitting a garbage frame to the network stack.
>
> Hm, you're right. /me smacks head. Thanks for your comments Neil, they
> are very useful.
>
I'm glad, thank you for listening. I just couldn't reconcile what you were
saying with what the vulnerability was as it was reported.
> Wish we had thought to test the 1000 mtu case before I replied. In any
> case, we now have verified that the fix in this thread is good in the case
> of 1000 mtu.
>
Agreed, we've done so as well here.
> So I now withdraw my withdrawal.
>
> We have a couple more things to test/fix before we post the final
> version(s), I know this is priority but I also don't want to rush out an
> incomplete fix.
>
Don't rush, I expect distros can go with what we have currently if we need to
update later we can.
> Current plan is Jeff K will post the official version in the next couple
> of days, for e1000 and e1000e, which isn't necessary for >=1500 mtu, but
> is apparently necessary for smaller MTU.
>
Copy that, thanks!
Neil
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
prev parent reply other threads:[~2010-01-13 3:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-28 20:10 [PATCH] e1000: enhance frame fragment detection Neil Horman
2009-12-29 0:42 ` Jeff Kirsher
2009-12-29 1:14 ` Neil Horman
2010-01-05 21:44 ` Brandeburg, Jesse
2010-01-05 22:04 ` Neil Horman
2010-01-06 23:27 ` Brandeburg, Jesse
2010-01-07 0:56 ` Neil Horman
2010-01-13 1:56 ` Brandeburg, Jesse
2010-01-13 2:04 ` Ben Hutchings
2010-01-13 2:12 ` Neil Horman
2010-01-13 2:47 ` Brandeburg, Jesse
2010-01-13 3:33 ` Neil Horman [this message]
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=20100113033326.GA1931@localhost.localdomain \
--to=nhorman@tuxdriver.com \
--cc=bruce.w.allan@intel.com \
--cc=davem@davemloft.net \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=netdev@vger.kernel.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).