From: patchwork-bot+netdevbpf@kernel.org
To: Jeff Jo <jeffjo@openai.com>
Cc: netdev@vger.kernel.org, edumazet@google.com,
ncardwell@google.com, kuniyu@google.com, davem@davemloft.net,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
shuah@kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net v2 0/2] tcp: correct timestamp echo for accepted old ACKs
Date: Wed, 30 Sep 2026 07:20:06 +0000 [thread overview]
Message-ID: <179075280628.1300549.5509783868207806215.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260924224456.55690-4-jeffjo@openai.com>
Hello:
This series was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 24 Sep 2026 15:44:57 -0700 you wrote:
> Linux can acknowledge newly received data while echoing an outdated
> TCP timestamp. This happens when a reordered packet fills a receive gap
> but carries an older acknowledgment for traffic in the other direction.
> If the sender uses this echo to measure round-trip time after a long idle
> period, the stale timestamp can inflate its estimate and slow its sending.
>
> Changes in v2, following Eric Dumazet's review:
> - Remove the redundant SYN_RECV condition and unused flag accumulation.
> - Replace the log-parsing wrapper with a plain packetdrill test that checks
> the timestamp echo directly, using the existing selftest runner.
> - Rebase on net fc6d80eb5044.
>
> [...]
Here is the summary with links:
- [net,v2,1/2] tcp: refresh TS.Recent for accepted old ACKs
https://git.kernel.org/netdev/net/c/1b92780ae4fc
- [net,v2,2/2] selftests: net: check timestamp echo after an old ACK
https://git.kernel.org/netdev/net/c/81fe707ae58e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-30 7:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 22:44 Jeff Jo
2026-09-24 22:44 ` [PATCH net v2 1/2] tcp: refresh TS.Recent " Jeff Jo
2026-09-25 0:57 ` Eric Dumazet
2026-09-24 22:44 ` [PATCH net v2 2/2] selftests: net: check timestamp echo after an old ACK Jeff Jo
2026-09-25 0:58 ` Eric Dumazet
2026-09-25 22:47 ` netdev-bot+sashiko
2026-09-28 17:47 ` Jeff Jo
2026-09-30 7:20 ` patchwork-bot+netdevbpf [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=179075280628.1300549.5509783868207806215.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jeffjo@openai.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@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
all inboxes | Powered by JetHome®