lkml.org 
[lkml]   [1998]   [Nov]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
DateWed, 04 Nov 1998 09:26:46 -0500
FromPhilip Gladstone <>
SubjectRe: Weird TCP CLOSE state behavior
Jason,
I find that the attached patch works wonders for me. This is
against 2.0.35pre16, but it should apply to somewhat earlier versions.
I think that this patch is in the queue for 2.0.37, but Alan did not
deem this bug serious enough for 2.0.36.

Philip

Jason Gunthorpe wrote:
>
> [Please CC, I'm not on the list]
>
> Hi,
>
> I'm seeing some strange behavoir with some rsync processes. They somehow
> manage to get their connection stuck in the CLOSE state and never die, I
> now have some that have been sitting around for almost two days! I
> discussed the matter with Andrew and there is some speculation that it may
> be some weird kernel problem, here are the details..

--
Philip Gladstone +1 781 530 2461
Raptor Systems / Axent Technologies
Waltham, MA http://www.raptor.com/--- olinux/net/ipv4/tcp.c Wed Aug 5 13:58:44 1998
+++ linux/net/ipv4/tcp.c Wed Aug 5 13:51:45 1998
@@ -951,6 +951,7 @@
return 0;
- if (sk->state == TCP_SYN_SENT || sk->state == TCP_SYN_RECV)
- break;
+ /* Check do_tcp_sendmsg for this next line */
+ if (sk->state != TCP_ESTABLISHED && sk->state != TCP_CLOSE_WAIT)
+ break;
if (sk->wmem_alloc*2 > sk->sndbuf)
break;
return 1;[unhandled content-type:application/x-pkcs7-signature]
\
 
 \ /
  Last update: 2005-03-22 13:45    [from the cache]
©2003-2010