From: David Miller <davem@davemloft.net>
To: jeffrey.t.kirsher@intel.com
Cc: netdev@vger.kernel.org, gospo@redhat.com, jesse.brandeburg@intel.com
Subject: Re: [net-2.6 PATCH] e1000/e1000e: don't use small hardware rx buffers
Date: Sat, 23 Jan 2010 01:07:56 -0800 (PST) [thread overview]
Message-ID: <20100123.010756.67415950.davem@davemloft.net> (raw)
In-Reply-To: <20100123085550.10383.68204.stgit@localhost.localdomain>
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Date: Sat, 23 Jan 2010 00:56:16 -0800
> From: Jesse Brandeburg <jesse.brandeburg@intel.com>
>
> When testing the "e1000: enhance frame fragment detection" (and e1000e)
> patches we found some bugs with reducing the MTU size. The 1024 byte
> descriptor used with the 1000 mtu test also (re) introduced the
> (originally) reported bug, and causes us to need the e1000_clean_tx_irq
> "enhance frame fragment detection" fix.
>
> So what has occured here is that 2.6.32 is only vulnerable for mtu <
> 1500 due to the jumbo specific routines in both e1000 and e1000e.
> So, 2.6.32 needs the 2kB buffer len fix for those smaller MTUs, but
> is not vulnerable to the original issue reported. It has been pointed
> out that this vulnerability needs to be patched in older kernels that
> don't have the e1000 jumbo routine. Without the jumbo routines, we
> need the "enhance frame fragment detection" fix the e1000, old
> e1000e is only vulnerable for < 1500 mtu, and needs a similar
> fix. We split the patches up to provide easy backport paths.
>
> There is only a slight bit of extra code when this fix and the
> original "enhance frame fragment detection" fixes are applied, so
> please apply both, even though it is a bit of overkill.
>
> Signed-off-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Applied.
prev parent reply other threads:[~2010-01-23 9:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-23 8:56 [net-2.6 PATCH] e1000/e1000e: don't use small hardware rx buffers Jeff Kirsher
2010-01-23 9:07 ` David Miller [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=20100123.010756.67415950.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=gospo@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@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).