netdev - Re: TCP stalls in current git, possibly splice related

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 16 Jul 2007 14:02:47 +0200
From:	Jens Axboe <jens.axboe@...cle.com>
To:	Johannes Berg <johannes@...solutions.net>
Cc:	James Morris <jmorris@...ei.org>,
	"David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org
Subject: Re: TCP stalls in current git, possibly splice related

On Mon, Jul 16 2007, Johannes Berg wrote:
> On Fri, 2007-07-13 at 13:05 +0200, Jens Axboe wrote:
> > On Fri, Jul 13 2007, Johannes Berg wrote:
> > > On Thu, 2007-07-12 at 16:12 -0400, James Morris wrote:
> > > > I'm seeing TCP connection stalls with current git, and a bisect found the 
> > > > following as a possible cause:
> > > 
> > > I'm also seeing stalls with synergy.
> > 
> > Please try the below.
> 
> I usually see stalls sending data from machine A to machine B. I just
> upgraded machine B to commit 8d9107e8c50e1c4ff43c91c8841805833f3ecfb9
> (Fri Jul 13 16:53:18 2007 -0700) and the tree includes this patch. This
> did not, however, fix the problem so I guess the problem is on the
> sender side. Due to wireless-dev lagging behind I there still have
> 2.6.22-something where this patch doesn't apply. I hope John will merge
> again soon and then I'll report back whether I still see the stalling
> behaviour with a current tree that includes this patch.

Yep, it's a sender thing, so upgrading the receiver will not change
anything.

-- 
Jens Axboe

-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html