netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kuniyuki Iwashima <kuniyu@google.com>
To: Eric Dumazet <edumazet@google.com>,
	Neal Cardwell <ncardwell@google.com>,
	 "David S . Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: Simon Horman <horms@kernel.org>,
	Yuchung Cheng <ycheng@google.com>,
	 Kuniyuki Iwashima <kuniyu@google.com>,
	Kuniyuki Iwashima <kuni1840@gmail.com>,
	netdev@vger.kernel.org
Subject: [PATCH v1 net-next 3/6] tcp: Remove redundant init for req->num_timeout.
Date: Thu,  6 Nov 2025 00:32:42 +0000	[thread overview]
Message-ID: <20251106003357.273403-4-kuniyu@google.com> (raw)
In-Reply-To: <20251106003357.273403-1-kuniyu@google.com>

Commit 5903123f662e ("tcp: Use BPF timeout setting for SYN ACK
RTO") introduced req->timeout and initialised it in 3 places:

  1. reqsk_alloc() sets 0
  2. inet_reqsk_alloc() sets TCP_TIMEOUT_INIT
  3. tcp_conn_request() sets tcp_timeout_init()

1. has been always redundant as 2. overwrites it immediately.

2. was necessary for TFO SYN+ACK but is no longer needed after
commit 8ea731d4c2ce ("tcp: Make SYN ACK RTO tunable by BPF
programs with TFO").

3. was moved to reqsk_queue_hash_req() in the previous patch.

Now, we always initialise req->timeout just before scheduling
the SYN+ACK timer:

  * For non-TFO SYN+ACK : reqsk_queue_hash_req()
  * For TFO SYN+ACK     : tcp_fastopen_create_child()

Let's remove the redundant initialisation of req->timeout in
reqsk_alloc() and inet_reqsk_alloc().

Signed-off-by: Kuniyuki Iwashima <kuniyu@google.com>
---
 net/ipv4/inet_connection_sock.c | 2 --
 1 file changed, 2 deletions(-)

diff --git a/net/ipv4/inet_connection_sock.c b/net/ipv4/inet_connection_sock.c
index d9c674403eb0..2bfe7af51bbb 100644
--- a/net/ipv4/inet_connection_sock.c
+++ b/net/ipv4/inet_connection_sock.c
@@ -885,7 +885,6 @@ reqsk_alloc_noprof(const struct request_sock_ops *ops, struct sock *sk_listener,
 	sk_tx_queue_clear(req_to_sk(req));
 	req->saved_syn = NULL;
 	req->syncookie = 0;
-	req->timeout = 0;
 	req->num_timeout = 0;
 	req->num_retrans = 0;
 	req->sk = NULL;
@@ -913,7 +912,6 @@ struct request_sock *inet_reqsk_alloc(const struct request_sock_ops *ops,
 		ireq->ireq_state = TCP_NEW_SYN_RECV;
 		write_pnet(&ireq->ireq_net, sock_net(sk_listener));
 		ireq->ireq_family = sk_listener->sk_family;
-		req->timeout = TCP_TIMEOUT_INIT;
 	}
 
 	return req;
-- 
2.51.2.1026.g39e6a42477-goog


  parent reply	other threads:[~2025-11-06  0:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-06  0:32 [PATCH v1 net-next 0/6] tcp: Clean up SYN+ACK RTO code and apply max RTO Kuniyuki Iwashima
2025-11-06  0:32 ` [PATCH v1 net-next 1/6] tcp: Call tcp_syn_ack_timeout() directly Kuniyuki Iwashima
2025-11-07  8:00   ` Eric Dumazet
2025-11-06  0:32 ` [PATCH v1 net-next 2/6] tcp: Remove timeout arg from reqsk_queue_hash_req() Kuniyuki Iwashima
2025-11-07  8:03   ` Eric Dumazet
2025-11-06  0:32 ` Kuniyuki Iwashima [this message]
2025-11-07  8:37   ` [PATCH v1 net-next 3/6] tcp: Remove redundant init for req->num_timeout Eric Dumazet
2025-11-06  0:32 ` [PATCH v1 net-next 4/6] tcp: Remove timeout arg from reqsk_timeout() Kuniyuki Iwashima
2025-11-07  8:39   ` Eric Dumazet
2025-11-06  0:32 ` [PATCH v1 net-next 5/6] tcp: Apply max RTO to non-TFO SYN+ACK Kuniyuki Iwashima
2025-11-07  8:41   ` Eric Dumazet
2025-11-06  0:32 ` [PATCH v1 net-next 6/6] selftest: packetdrill: Add max RTO test for SYN+ACK Kuniyuki Iwashima
2025-11-07  8:43   ` Eric Dumazet
2025-11-08  2:20 ` [PATCH v1 net-next 0/6] tcp: Clean up SYN+ACK RTO code and apply max RTO 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=20251106003357.273403-4-kuniyu@google.com \
    --to=kuniyu@google.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuni1840@gmail.com \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=ycheng@google.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;
as well as URLs for NNTP newsgroup(s).