From: Jakub Sitnicki <jakub@cloudflare.com>
To: netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
Jason Xing <kerneljasonxing@gmail.com>,
Adrien Vasseur <avasseur@cloudflare.com>,
Lee Valentine <lvalentine@cloudflare.com>,
kernel-team@cloudflare.com
Subject: Re: [PATCH net-next v2 0/2] Make TIME-WAIT reuse delay deterministic and configurable
Date: Fri, 13 Dec 2024 14:06:46 +0100 [thread overview]
Message-ID: <87ed2bu3yx.fsf@cloudflare.com> (raw)
In-Reply-To: <20241209-jakub-krn-909-poc-msec-tw-tstamp-v2-0-66aca0eed03e@cloudflare.com> (Jakub Sitnicki's message of "Mon, 09 Dec 2024 20:38:02 +0100")
On Mon, Dec 09, 2024 at 08:38 PM +01, Jakub Sitnicki wrote:
> Packetdrill tests
> -----------------
>
> The packetdrill tests for TIME-WAIT reuse [3] did not change since v1.
> Although we are not touching PAWS code any more, I would still like to add
> tests to cover PAWS reject after TW reuse. This, however, requires patching
> packetdrill as I mentioned in the last cover letter [2].
Thank you for the prompt reviews. Happy to hear there are other users
looking to adopt these.
Since patches are now in net-next, I have moved the accompanying
packetdrill PR from Draft to Open, if you want to follow that work:
https://github.com/google/packetdrill/pull/90
prev parent reply other threads:[~2024-12-13 13:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 19:38 [PATCH net-next v2 0/2] Make TIME-WAIT reuse delay deterministic and configurable Jakub Sitnicki
2024-12-09 19:38 ` [PATCH net-next v2 1/2] tcp: Measure TIME-WAIT reuse delay with millisecond precision Jakub Sitnicki
2024-12-10 8:11 ` Eric Dumazet
2024-12-12 1:00 ` Jason Xing
2024-12-09 19:38 ` [PATCH net-next v2 2/2] tcp: Add sysctl to configure TIME-WAIT reuse delay Jakub Sitnicki
2024-12-10 8:21 ` Eric Dumazet
2024-12-12 1:08 ` Jason Xing
2024-12-12 4:30 ` [PATCH net-next v2 0/2] Make TIME-WAIT reuse delay deterministic and configurable patchwork-bot+netdevbpf
2024-12-13 13:06 ` Jakub Sitnicki [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=87ed2bu3yx.fsf@cloudflare.com \
--to=jakub@cloudflare.com \
--cc=avasseur@cloudflare.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kernel-team@cloudflare.com \
--cc=kerneljasonxing@gmail.com \
--cc=kuba@kernel.org \
--cc=lvalentine@cloudflare.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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.