public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lutz Vieweg <lvml@5t9.de>
To: linux-kernel@vger.kernel.org
Subject: connect() stalls after 4.9 -> 4.10 upgrade
Date: Mon, 27 Feb 2017 15:19:23 +0100	[thread overview]
Message-ID: <o91ch5$l9n$1@blaine.gmane.org> (raw)

Hi all,

the following regression a colleage and me experienced on two different
machines after upgrading from linux-4.9 to linux-4.10 is so obvious and
so easy to reproduce that I am surprised we could not find any reports
of it on the Internet:

After upgrading a machine running the latest CentOS from using mainline
kernel linux-4.9 to linux-4.10, attempts to connect() via IPv4 to localhost
(and seemingly also other hosts) fail in about half of the cases, leaving
the process trying to connect() stalled until timeout.

Reproduction:

 > ncat -k -l 19999 &
 > C=1 ; while true ; do echo -n "$C " ; echo ping | ncat localhost 19999 ; C=`expr $C + 1` ; sleep 
1 ; done

Using linux-4.10, the output looks like this:

 > 1 ping
 > 2 Ncat: Connection timed out.
 > 3 ping
 > 4 Ncat: Connection timed out.
 > 5 ping
 > 6 ping
 > 7 ping
 > 8 Ncat: Connection timed out.
 > 9 ping
 > 10 ping
 > 11 Ncat: Connection timed out.
 > 12 ping
 > 13 Ncat: Connection timed out.
 > 14 ping
 > 15 Ncat: Connection timed out.
 > 16 ping
 > 17 Ncat: Connection timed out.
 > 18 ping
 > 19 ping
 > 20 Ncat: Connection timed out.
 > 21 ping
 > 22 ping
 > 23 Ncat: Connection timed out.
 > 24 ping
 > 25 Ncat: Connection timed out.
 > 26 Ncat: Connection timed out.
 > 27 ping
 > 28 Ncat: Connection timed out.
 > 29 ping


Using linux-4.9, the output looks like this:

 > 1 ping
 > 2 ping
 > 3 ping
 > 4 ping
 > 5 ping
 > 6 ping
 > 7 ping
 > 8 ping
 > 9 ping
 > 10 ping
 > 11 ping
 > 12 ping
 > 13 ping
 > 14 ping
 > 15 ping
 > 16 ping
 > 17 ping
 > 18 ping
 > 19 ping

The two machines we observed this symptom on were running
different distributions (CentOS 7.3 and Ubuntu) and were of
completely different hardware.

Didn't anybody else experience the same symptom?

(I also created https://bugzilla.kernel.org/show_bug.cgi?id=194723 on this topic.)

Regards,

Lutz Vieweg

             reply	other threads:[~2017-02-27 14:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-27 14:19 Lutz Vieweg [this message]
2017-03-15 19:48 ` change "tcp: randomize tcp timestamp offsets for each connection" broke networking Lutz Vieweg
2017-03-16  2:49   ` Mike Galbraith

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='o91ch5$l9n$1@blaine.gmane.org' \
    --to=lvml@5t9.de \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox