From: Neil Horman <nhorman@tuxdriver.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
jesse.brandeburg@intel.com, bruce.w.allan@intel.com,
peter.p.waskiewicz.jr@intel.com, john.ronciak@intel.com,
e1000-devel@lists.sourceforge.net
Subject: Re: [PATCH] e1000: enhance frame fragment detection
Date: Mon, 28 Dec 2009 20:14:39 -0500 [thread overview]
Message-ID: <20091229011439.GB7037@localhost.localdomain> (raw)
In-Reply-To: <9929d2390912281642o964617kbee6e8a2b9f6c75f@mail.gmail.com>
On Mon, Dec 28, 2009 at 04:42:09PM -0800, Jeff Kirsher wrote:
> On Mon, Dec 28, 2009 at 12:10, Neil Horman <nhorman@tuxdriver.com> wrote:
> > Hey all-
> > A security discussion was recently given:
> > http://events.ccc.de/congress/2009/Fahrplan//events/3596.en.html
> > And a patch that I submitted awhile back was brought up. Apparently some of
> > their testing revealed that they were able to force a buffer fragment in e1000
> > in which the trailing fragment was greater than 4 bytes. As a result the
> > fragment check I introduced failed to detect the fragement and a partial invalid
> > frame was passed up into the network stack. I've written this patch to correct
> > it. I'm in the process of testing it now, but it makes good logical sense to
> > me. Effectively it maintains a per-adapter state variable which detects a
> > non-EOP frame, and discards it and subsequent non-EOP frames leading up to _and_
> > _including_ the next positive-EOP frame (as it is by definition the last
> > fragment). This should prevent any and all partial frames from entering the
> > network stack from e1000
> >
> > Regards
> > Neil
> >
> >
> > e1000.h | 3 ++-
> > e1000_main.c | 14 ++++++++++++--
> > 2 files changed, 14 insertions(+), 3 deletions(-)
> >
> >
>
> Thanks Neil. I have add the patch to my queue of patches.
>
> --
> Cheers,
> Jeff
>
Thanks jeff, much appreciated
Happy Holidays
Neil
next prev parent reply other threads:[~2009-12-29 1:14 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 [this message]
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
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=20091229011439.GB7037@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 \
--cc=peter.p.waskiewicz.jr@intel.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