All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrey Dmitrov <andrey.dmitrov@oktetlabs.ru>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Hannes Frederic Sowa <hannes@stressinduktion.org>,
	netdev@vger.kernel.org,
	"Alexandra N. Kossovsky" <Alexandra.Kossovsky@oktetlabs.ru>,
	Konstantin Ushakov <kostik@oktetlabs.ru>
Subject: Re: TCP connection will hang in FIN_WAIT1 after closing if zero window is advertised
Date: Tue, 16 Sep 2014 18:08:15 +0400	[thread overview]
Message-ID: <5418444F.7010403@oktetlabs.ru> (raw)
In-Reply-To: <1410872966.7106.187.camel@edumazet-glaptop2.roam.corp.google.com>

On 16/09/14 17:09, Eric Dumazet wrote:
> 1) TCP_USER_TIMEOUT would be the fit for this, but its current
> implementation do not take care of the probes sent, even in FIN_WAIT
> state when in this zero window mode. A patch would be needed.
>
> 2) SO_LINGER, timeout=0 might work.
I tried to set SO_LINGER with non-zero timeout before reporting the bug, 
it did not help. But I've just tried again with the zero timeout 
(l_linger=0) and it works, the connection has been interrupted 
immediately after socket closing, RST packet has been sent. It seems 
like a bug, SO_LINGER with non-zero timeout does not interrupt the 
connection.

Thanks,
Andrey

  reply	other threads:[~2014-09-16 14:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-15 16:11 TCP connection will hang in FIN_WAIT1 after closing if zero window is advertised Andrey Dmitrov
2014-09-15 19:43 ` Neal Cardwell
2014-09-16  9:29   ` Andrey Dmitrov
2014-09-15 23:15 ` Hannes Frederic Sowa
2014-09-15 23:37   ` Yuchung Cheng
2014-09-16 12:49     ` Andrey Dmitrov
2014-09-16  1:50   ` Eric Dumazet
2014-09-16  8:37     ` Hannes Frederic Sowa
2014-09-16 12:47   ` Andrey Dmitrov
2014-09-16 13:09     ` Eric Dumazet
2014-09-16 14:08       ` Andrey Dmitrov [this message]
2014-09-16 15:11       ` Yuchung Cheng
2014-09-16 16:31         ` Neal Cardwell
2014-09-16 17:04           ` Eric Dumazet

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=5418444F.7010403@oktetlabs.ru \
    --to=andrey.dmitrov@oktetlabs.ru \
    --cc=Alexandra.Kossovsky@oktetlabs.ru \
    --cc=eric.dumazet@gmail.com \
    --cc=hannes@stressinduktion.org \
    --cc=kostik@oktetlabs.ru \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.