netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Guillaume Nault <gnault@redhat.com>,
	David Miller <davem@davemloft.net>,
	Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: netdev@vger.kernel.org, Eric Dumazet <edumazet@google.com>,
	Arnd Bergmann <arnd@arndb.de>,
	John Stultz <john.stultz@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH net v4 1/3] tcp: fix rejected syncookies due to stale timestamps
Date: Fri, 6 Dec 2019 17:49:51 -0800	[thread overview]
Message-ID: <3eaa158d-32e6-d541-d0fc-d1b79738f84f@gmail.com> (raw)
In-Reply-To: <b1e80e43ba300a37ac5ea70088769fbe8ac5bf01.1575631229.git.gnault@redhat.com>



On 12/6/19 3:38 AM, Guillaume Nault wrote:
> If no synflood happens for a long enough period of time, then the
> synflood timestamp isn't refreshed and jiffies can advance so much
> that time_after32() can't accurately compare them any more.
...
> 
> Fixes: cca9bab1b72c ("tcp: use monotonic timestamps for PAWS")
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Signed-off-by: Guillaume Nault <gnault@redhat.com>

Signed-off-by: Eric Dumazet <edumazet@google.com>


  reply	other threads:[~2019-12-07  1:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-06 11:38 [PATCH net v4 0/3] tcp: fix handling of stale syncookies timestamps Guillaume Nault
2019-12-06 11:38 ` [PATCH net v4 1/3] tcp: fix rejected syncookies due to stale timestamps Guillaume Nault
2019-12-07  1:49   ` Eric Dumazet [this message]
2019-12-06 11:38 ` [PATCH net v4 2/3] tcp: tighten acceptance of ACKs not matching a child socket Guillaume Nault
2019-12-06 11:38 ` [PATCH net v4 3/3] tcp: Protect accesses to .ts_recent_stamp with {READ,WRITE}_ONCE() Guillaume Nault
2019-12-07  5:06 ` [PATCH net v4 0/3] tcp: fix handling of stale syncookies timestamps David Miller

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=3eaa158d-32e6-d541-d0fc-d1b79738f84f@gmail.com \
    --to=eric.dumazet@gmail.com \
    --cc=arnd@arndb.de \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gnault@redhat.com \
    --cc=jakub.kicinski@netronome.com \
    --cc=john.stultz@linaro.org \
    --cc=netdev@vger.kernel.org \
    --cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).