All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Florian Westphal <fw@strlen.de>, netdev@vger.kernel.org
Subject: Re: [RFC 1/3] tcp: randomize tcp timestamp offsets for each connection
Date: Thu, 25 Aug 2016 22:31:25 +0200	[thread overview]
Message-ID: <20160825203125.GA10987@breakpoint.cc> (raw)
In-Reply-To: <1472153655.14381.152.camel@edumazet-glaptop3.roam.corp.google.com>

Eric Dumazet <eric.dumazet@gmail.com> wrote:
> On Thu, 2016-08-18 at 14:48 +0200, Florian Westphal wrote:
> It seems tcp_v4_reqsk_send_ack() and tcp_v6_reqsk_send_ack() were not
> taken into account.
> 
> See commit 20a2b49fc5385 changelog
> packetdrill test showing the possible issue if the TS sent on an ACK in
> SYN_RECV state is wrong.

Thanks a lot Eric, I'll fix this.

  reply	other threads:[~2016-08-25 20:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-18 12:48 [RFC 0/3] tcp: increase resilence vs. blind data injection Florian Westphal
2016-08-18 12:48 ` [RFC 1/3] tcp: randomize tcp timestamp offsets for each connection Florian Westphal
2016-08-18 16:18   ` Eric Dumazet
2016-08-18 22:32     ` Florian Westphal
2016-08-25  9:06     ` Florian Westphal
2016-08-25 14:15       ` Eric Dumazet
2016-08-25 14:49         ` Florian Westphal
2016-08-25 16:05           ` Eric Dumazet
2016-08-25 19:34   ` Eric Dumazet
2016-08-25 20:31     ` Florian Westphal [this message]
2016-08-25 21:06       ` Eric Dumazet
2016-08-25 22:06   ` Eric Dumazet
2016-08-25 23:46     ` Florian Westphal
2016-08-26  2:34       ` Eric Dumazet
2016-08-18 12:48 ` [RFC 2/3] tcp: add tcp_timestamps=2 mode to force tsecr validation on ofo segments Florian Westphal
2016-08-18 12:48 ` [RFC 3/3] tcp: add mib counter to track ts tsecr validation failures Florian Westphal

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=20160825203125.GA10987@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=eric.dumazet@gmail.com \
    --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.