| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <pan.2007.12.02.16.00.03.568000@wizards.de> Date: Sun, 02 Dec 2007 17:00:03 +0100 From: "Holger Hoffstaette" <holger@...ards.de> To: linux-kernel@...r.kernel.org Cc: netdev@...r.kernel.org Subject: Re: Reproducible data corruption with sendfile+vsftp - splice regression? 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? thank you Holger -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists