netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brandon Philips <brandon@ifup.org>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Neil Horman <nhorman@tuxdriver.com>,
	David Miller <davem@davemloft.net>,
	ben@decadent.org.uk, eric.dumazet@gmail.com,
	netdev@vger.kernel.org
Subject: Re: [PATCH RFC] r8169: straighten out overlength frame detection (v3)
Date: Thu, 18 Feb 2010 11:37:33 -0800	[thread overview]
Message-ID: <20100218193733.GA23337@jenkins.home.ifup.org> (raw)
In-Reply-To: <20100130215026.GA6146@localhost.localdomain>

On 16:50 Sat 30 Jan 2010, Neil Horman wrote:
> On Tue, Jan 12, 2010 at 01:16:46AM +0100, Francois Romieu wrote:
> > On Sun, Jan 10, 2010 at 10:45:04PM -0800, David Miller wrote:
> > [...]
> > > In my opinion if you reset, you give them more power.
> > > 
> > > Instead of just dropping the next few frames, you allow them
> > > to cause a drop of how ever many RX frames can arrive during
> > > the reset period _PLUS_ the amount of other RX frames which
> > > were in the receive ring at the point of detection.
> > 
> > Sure.
> > 
> > The fragmented frame test has been moved a few lines up, before checking
> > for the status bits. Exceedingly small frames are detected and dropped
> > as well.
> > 
> > I have spent the evening disrupting the communication. As a challenger
> > one does not even need complete control : send a few random packets and
> > the card goes to neverland. :o/
> > 
> > I'll do some tests limiting the crap at the first packet.
> > 
> Any further results you can share with us Francois?

Can I offer any help? I found that I have access to a Rev 0x10 card.

Cheers,

	Brandon

      reply	other threads:[~2010-02-18 19:37 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-28 19:48 [PATCH RFC] r8169: straighten out overlength frame detection Neil Horman
2009-12-28 19:50 ` Neil Horman
2009-12-28 21:31   ` François romieu
2009-12-28 23:49     ` Neil Horman
2009-12-29  0:24     ` David Dillow
2009-12-29  1:20       ` Neil Horman
2009-12-29  0:51     ` Ben Hutchings
2009-12-29  1:16       ` Neil Horman
2009-12-29  1:29         ` Ben Hutchings
2009-12-29 15:35     ` Neil Horman
2010-01-05 13:57 ` [PATCH RFC] r8169: straighten out overlength frame detection (v3) Neil Horman
2010-01-05 15:15   ` Eric Dumazet
2010-01-05 20:40     ` David Miller
2010-01-05 21:38       ` Neil Horman
2010-01-05 21:45         ` David Miller
2010-01-05 22:04           ` Neil Horman
2010-01-07  1:01       ` Francois Romieu
2010-01-07  1:15         ` David Miller
2010-01-08 23:48           ` Francois Romieu
2010-01-09  0:02             ` David Miller
2010-01-10  1:57               ` Ben Hutchings
2010-01-10 23:50                 ` Francois Romieu
2010-01-11  6:45                   ` David Miller
2010-01-12  0:16                     ` Francois Romieu
2010-01-12  6:24                       ` David Miller
2010-01-26 22:07                         ` Brandon Philips
2010-01-30 21:50                       ` Neil Horman
2010-02-18 19:37                         ` Brandon Philips [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=20100218193733.GA23337@jenkins.home.ifup.org \
    --to=brandon@ifup.org \
    --cc=ben@decadent.org.uk \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=romieu@fr.zoreil.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;
as well as URLs for NNTP newsgroup(s).