netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Holger Hoffstaette" <holger@wizards.de>
To: netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Reproducible data corruption with sendfile+vsftp - splice regression?
Date: Sun, 02 Dec 2007 21:49:42 +0100	[thread overview]
Message-ID: <pan.2007.12.02.20.49.42.675000@wizards.de> (raw)
In-Reply-To: pan.2007.12.02.16.00.03.568000@wizards.de

On Sun, 02 Dec 2007 17:00:03 +0100, Holger Hoffstaette wrote:

> On Fri, 30 Nov 2007 10:26:54 -0800, Rick Jones wrote:
> 
>> Could the corruption be seen in a tcpdump trace prior to transmission
>> (ie taken on the sender) or was it only seen after the data passed out
>> the NIC?
> 
> I did the following:
> 
> 1) turn on tso on the server's r8169: ethtool --offload eth0 tso on
> 2) on the server: tcpdump -i eth0 -s 0 -w <file>
> 3) ftp'ed file to 100mbit client
> 
> As expected the file was corrupted, and the various corrupted byte
> sequences also show up in the tcpdump file at the corresponding offsets.
> 
> I did this with 2.6.22.14, so it does not seem to be a recent regression
> in .23/.24.
> 
> All files can be found here:
> http://hoho.dyndns.org/~holger/dist/r8169-tso/
> 
> I will gladly try out any other tweaks but need some guidance as I don't
> know what exactly to change - maybe without NAPI for the r8169?

Ta-daa! Rebuilding 2.6.22.14 (and I suspect all other versions) without
NAPI for the r8169 but with tso enabled yields NO data corruption; the
ftp'ed file has a good crc, repeatedly.

Any suggestions how to proceed? Should I file this in bugzilla?

thanks
Holger



  reply	other threads:[~2007-12-02 20:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <pan.2007.11.29.23.42.52.661624@wizards.de>
2007-11-30  8:07 ` Reproducible data corruption with sendfile+vsftp - splice regression? Eric Dumazet
2007-11-30  9:20   ` Holger Hoffstaette
2007-11-30 10:39     ` Holger Hoffstaette
2007-11-30 18:26     ` Rick Jones
2007-12-02 16:00       ` Holger Hoffstaette
2007-12-02 20:49         ` Holger Hoffstaette [this message]
2007-12-05 22:54           ` Francois Romieu
2007-12-06  1:13             ` Francois Romieu
2007-12-06  9:41               ` Holger Hoffstaette
2007-12-06  9:28             ` Holger Hoffstaette
2007-12-06 18:44               ` Francois Romieu
2007-12-08 15:28                 ` Mark Lord
2007-12-13  2:19                 ` Holger Hoffstaette
2007-12-15 10:24                   ` Holger Hoffstaette
2007-12-15 13:43                 ` Holger Hoffstaette

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=pan.2007.12.02.20.49.42.675000@wizards.de \
    --to=holger@wizards.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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).