public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <edumazet@google.com>
To: "David S . Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	 Paolo Abeni <pabeni@redhat.com>
Cc: Simon Horman <horms@kernel.org>,
	Neal Cardwell <ncardwell@google.com>,
	 Kuniyuki Iwashima <kuniyu@google.com>,
	netdev@vger.kernel.org, eric.dumazet@gmail.com,
	 Eric Dumazet <edumazet@google.com>
Subject: [PATCH net-next 0/2] tcp: tcp_tx_timestamp() fix
Date: Tue, 27 Jan 2026 12:38:26 +0000	[thread overview]
Message-ID: <20260127123828.4098577-1-edumazet@google.com> (raw)

Fix an old bug in tcp_tx_timestamp().

Add one corresponding packetdrill test.

Eric Dumazet (2):
  tcp: tcp_tx_timestamp() must look at the rtx queue
  selftest: packetdrill: add tcp_timestamping_tcp_tx_timestamp_bug.pkt

 net/ipv4/tcp.c                                |  3 +
 .../tcp_timestamping_tcp_tx_timestamp_bug.pkt | 70 +++++++++++++++++++
 2 files changed, 73 insertions(+)
 create mode 100644 tools/testing/selftests/net/packetdrill/tcp_timestamping_tcp_tx_timestamp_bug.pkt

-- 
2.53.0.rc1.217.geba53bf80e-goog


             reply	other threads:[~2026-01-27 12:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-27 12:38 Eric Dumazet [this message]
2026-01-27 12:38 ` [PATCH net-next 1/2] tcp: tcp_tx_timestamp() must look at the rtx queue Eric Dumazet
2026-01-28  2:22   ` Jason Xing
2026-01-27 12:38 ` [PATCH net-next 2/2] selftest: packetdrill: add tcp_timestamping_tcp_tx_timestamp_bug.pkt Eric Dumazet
2026-01-28  2:24   ` Jason Xing
2026-01-29  3:50 ` [PATCH net-next 0/2] tcp: tcp_tx_timestamp() fix patchwork-bot+netdevbpf

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=20260127123828.4098577-1-edumazet@google.com \
    --to=edumazet@google.com \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=ncardwell@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox