netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@bfk.de>
To: Urs Thuermann <urs@isnogud.escape.de>
Cc: Bill Fink <billfink@mindspring.com>,
	"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
	"L F" <lfabio.linux@gmail.com>,
	"Kok, Auke-jan H" <auke-jan.h.kok@intel.com>,
	"James Chapman" <jchapman@katalix.com>, <netdev@vger.kernel.org>
Subject: Re: e1000 driver and samba
Date: Tue, 18 Sep 2007 15:39:59 +0200	[thread overview]
Message-ID: <82k5qoxfbk.fsf@mid.bfk.de> (raw)
In-Reply-To: <ygfps0g8lj0.fsf@janus.isnogud.escape.de> (Urs Thuermann's message of "18 Sep 2007 09:45:07 +0200")

* Urs Thuermann:

> How can a corrupted frame pass the TCP checksum check?

The TCP/IP checksums are extremely weak.  If the corruption is due to
defective SRAM or something like that, it's likely that it causes an
error pattern which is 16-bit-aligned.  And an even number of
16-bit-aligned bit flips is not detected by the TCP checksum. 8-(

Actually, nobody should use TCP without application-level checksums
for that reason.  But of course, there is HTTP.

-- 
Florian Weimer                <fweimer@bfk.de>
BFK edv-consulting GmbH       http://www.bfk.de/
Kriegsstraße 100              tel: +49-721-96201-1
D-76133 Karlsruhe             fax: +49-721-96201-99

  parent reply	other threads:[~2007-09-18 13:57 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-14  2:04 e1000 driver and samba L F
2007-09-14 17:18 ` Kok, Auke
2007-09-14 18:40   ` L F
2007-09-14 20:59     ` Kok, Auke
2007-09-15  0:37       ` L F
2007-09-15  5:09         ` Bill Fink
2007-09-15 12:27           ` L F
2007-09-15 12:44             ` L F
2007-09-15 17:44       ` James Chapman
2007-09-15 19:07         ` Kok, Auke
2007-09-16  4:06           ` L F
2007-09-16  5:04             ` Kok, Auke
2007-09-17 16:42               ` L F
2007-09-17 17:02                 ` Kok, Auke
2007-09-17 18:58                   ` L F
2007-09-17 21:01                     ` Brandeburg, Jesse
2007-09-18  6:03                       ` Bill Fink
2007-09-18  7:45                         ` Urs Thuermann
2007-09-18  8:47                           ` Bill Fink
2007-09-18 13:39                           ` Florian Weimer [this message]
2007-09-18 16:32                             ` L F
2007-09-18 17:04                               ` Tantilov, Emil S
2007-09-19 14:53                                 ` L F
2007-09-20  2:51                                   ` Bill Fink
2007-09-21 14:08                                     ` L F
2007-09-20  4:53                                   ` Bill Fink
2007-09-18 16:44                             ` Bill Fink
2007-09-17 18:02               ` Rick Jones
2007-09-17 18:51                 ` Kok, Auke
2007-09-16 16:24           ` James Chapman
2007-09-16 20:03             ` Kok, Auke
2007-09-16  4:07         ` L F
2007-09-14 18:26 ` Francois Romieu
2007-09-14 18:41   ` L F
  -- strict thread matches above, loose matches on Subject: below --
2007-09-20 23:30 Bruce Cole
2007-09-21 14:13 ` L F
2007-09-21 18:21   ` Bruce Cole
2007-09-21 21:49 ` Francois Romieu
2007-09-21 22:01   ` Bruce Cole
2007-09-21 22:41     ` Francois Romieu

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=82k5qoxfbk.fsf@mid.bfk.de \
    --to=fweimer@bfk.de \
    --cc=auke-jan.h.kok@intel.com \
    --cc=billfink@mindspring.com \
    --cc=jchapman@katalix.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=lfabio.linux@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=urs@isnogud.escape.de \
    /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).