From: Mike Galbraith <efault@gmx.de>
To: Lutz Vieweg <lvml@5t9.de>, linux-kernel@vger.kernel.org
Subject: Re: change "tcp: randomize tcp timestamp offsets for each connection" broke networking
Date: Thu, 16 Mar 2017 03:49:31 +0100 [thread overview]
Message-ID: <1489632571.4239.6.camel@gmx.de> (raw)
In-Reply-To: <58C99A9E.4080403@5t9.de>
On Wed, 2017-03-15 at 20:48 +0100, Lutz Vieweg wrote:
> Dear Linux Developers,
>
> change set "tcp: randomize tcp timestamp offsets for each connection"
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/co
> mmit/?id=95a22caee396cef0bb2ca8fafdd82966a49367bb
> broke networking for several users starting from linux-4.10 -
> connects (even to localhost) would just time out in many cases.
>
> See
> https://bugzilla.kernel.org/show_bug.cgi?id=194723
> for a detailed description and the "git bisect" log.
The netdev thread therein indicates that the fix is in the works...
-Mike
prev parent reply other threads:[~2017-03-16 2:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 14:19 connect() stalls after 4.9 -> 4.10 upgrade Lutz Vieweg
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 [this message]
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=1489632571.4239.6.camel@gmx.de \
--to=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lvml@5t9.de \
/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