netdev - Possible packet loss issue in recent net-next

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <EA929A9653AAE14F841771FB1DE5A1365FE42DE69D@rrsmsx501.amr.corp.intel.com>
Date:	Wed, 24 Feb 2010 12:59:06 -0700
From:	"Tantilov, Emil S" <emil.s.tantilov@...el.com>
To:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
CC:	"Brandeburg, Jesse" <jesse.brandeburg@...el.com>,
	"Duyck, Alexander H" <alexander.h.duyck@...el.com>,
	"davem@...emloft.net" <davem@...emloft.net>
Subject: Possible packet loss issue in recent net-next

In the last few pulls from net-next I am seeing an issue where sometimes a transfer would stall for about 30secs and then continue. I see this with simple commands like `rsh server uname -a` and ftp transfers. It happens with multiple drivers.

I have not done much digging into it yet, but just wanted to check if it's a known issue. I don't see this problem when testing with the torvalds tree.

Attached is a capture from the rsh session that fails. The "server" (190.1.15.5) is the system running net-next kernel.

Thanks,
Emil

Download attachment "client_bad_run2.cap" of type "application/octet-stream" (2361 bytes)

Download attachment "server_bad_run2.cap" of type "application/octet-stream" (2367 bytes)

Download attachment "merged2.cap" of type "application/octet-stream" (4704 bytes)