netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Horman <nhorman@tuxdriver.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: "François romieu" <romieu@zoreil.com>,
	netdev@vger.kernel.org, davem@davemloft.net,
	eric.dumazet@gmail.com, nhorman@redhat.com
Subject: Re: [PATCH RFC] r8169: straighten out overlength frame detection
Date: Mon, 28 Dec 2009 20:16:09 -0500	[thread overview]
Message-ID: <20091229011608.GC7037@localhost.localdomain> (raw)
In-Reply-To: <20091229005152.GV2721@decadent.org.uk>

On Tue, Dec 29, 2009 at 12:51:52AM +0000, Ben Hutchings wrote:
> On Mon, 2009-12-28 at 22:31 +0100, François romieu wrote:
> > (I'm back)
> > 
> > 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
> > 
> > Is there a paper ?
> [...]
> 
> 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 from
> the above page; see pages 74-87.  I suggest you ask the speaker if you
> need any more details.
> 
> Ben.
> 
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 shortly.
Neil

> -- 
> Ben Hutchings
> Always try to do things in chronological order;
> it's less confusing that way.



  reply	other threads:[~2009-12-29  1:16 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 [this message]
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

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=20091229011608.GC7037@localhost.localdomain \
    --to=nhorman@tuxdriver.com \
    --cc=ben@decadent.org.uk \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@redhat.com \
    --cc=romieu@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).