From: Bill Fink <billfink@mindspring.com>
To: Florian Weimer <fweimer@bfk.de>
Cc: Urs Thuermann <urs@isnogud.escape.de>,
"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 12:44:46 -0400 [thread overview]
Message-ID: <20070918124446.89100042.billfink@mindspring.com> (raw)
In-Reply-To: <82k5qoxfbk.fsf@mid.bfk.de>
On Tue, 18 Sep 2007, Florian Weimer wrote:
> * 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.
But in this specific case, IIRC there were _no_ receive checksum
errors seen, and it would seem odd that any bit corruption was
_always_ an even number of 16-bit-aligned bit flips.
Also, I don't know anything at all about the SAMBA fs/protocol, but
I would expect it would have some kind of stronger data integrity
capability that should catch such errors. Which would be another
reason implying the data corruption problem is above the network
layer, and perhaps a hardware error of some kind on the write path
to the disk (also could possibly be a software bug of some kind
in that path).
-Bill
next prev parent reply other threads:[~2007-09-18 16:45 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
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 [this message]
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=20070918124446.89100042.billfink@mindspring.com \
--to=billfink@mindspring.com \
--cc=auke-jan.h.kok@intel.com \
--cc=fweimer@bfk.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.