From: Vijay Subramanian <subramanian.vijay@gmail.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, edumazet@google.com, ncardwell@google.com,
Venkat Venkatsubra <venkat.x.venkatsubra@oracle.com>,
Elliott Hughes <enh@google.com>,
Vijay Subramanian <subramanian.vijay@gmail.com>
Subject: [PATCH net-next V2 1/1] tcp: Prevent needless syn-ack rexmt during TWHS
Date: Fri, 26 Oct 2012 01:05:50 -0700 [thread overview]
Message-ID: <1351238750-13611-1-git-send-email-subramanian.vijay@gmail.com> (raw)
Elliott Hughes <enh@google.com> saw strange behavior when server socket was not
calling accept(). Client was receiving SYN-ACK back even when socket on server
side was not yet available. Eric noted server sockets kept resending SYN_ACKS
and further investigation revealed the following problem.
If server socket is slow to accept() connections, request_socks can represent
connections for which the three-way handshake is already done. From client's
point of view, the connection is in ESTABLISHED state but on server side, socket
is not in accept_queue or ESTABLISHED state. When the syn-ack timer expires,
because of the order in which tests are performed, server can retransmit the
synack repeatedly. Following patch prevents the server from retransmitting the
synack needlessly (and prevents client from replying with ack). This reduces
traffic when server is slow to accept() connections.
If the server socket has received the third ack during connection establishment,
this is remembered in inet_rsk(req)->acked. The request_sock will expire in
around 30 seconds and will be dropped if it does not move into accept_queue.
With help from Eric Dumazet.
Reported-by: Eric Dumazet <edumazet@google.com>
Acked-by: Neal Cardwell <ncardwell@google.com>
Tested-by: Neal Cardwell <ncardwell@google.com>
Acked-by: Eric Dumazet <edumazet@google.com>
Signed-off-by: Vijay Subramanian <subramanian.vijay@gmail.com>
---
Changes from V1: Changed Reported-by tag and commit message. Added Acked-by and
Tested-by tags.
Ignoring "WARNING: line over 80 characters" in the interest of readability.
net/ipv4/inet_connection_sock.c | 5 ++---
1 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/net/ipv4/inet_connection_sock.c b/net/ipv4/inet_connection_sock.c
index d34ce29..4e8e52e 100644
--- a/net/ipv4/inet_connection_sock.c
+++ b/net/ipv4/inet_connection_sock.c
@@ -598,9 +598,8 @@ void inet_csk_reqsk_queue_prune(struct sock *parent,
&expire, &resend);
req->rsk_ops->syn_ack_timeout(parent, req);
if (!expire &&
- (!resend ||
- !req->rsk_ops->rtx_syn_ack(parent, req, NULL) ||
- inet_rsk(req)->acked)) {
+ (!resend || inet_rsk(req)->acked ||
+ !req->rsk_ops->rtx_syn_ack(parent, req, NULL))) {
unsigned long timeo;
if (req->retrans++ == 0)
--
1.7.0.4
next reply other threads:[~2012-10-26 7:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 8:05 Vijay Subramanian [this message]
2012-10-26 8:03 ` [PATCH net-next V2 1/1] tcp: Prevent needless syn-ack rexmt during TWHS Eric Dumazet
2012-10-26 21:30 ` Julian Anastasov
2012-10-26 21:42 ` Eric Dumazet
2012-10-26 22:52 ` Julian Anastasov
2012-10-27 0:07 ` Vijay Subramanian
2012-10-27 8:43 ` Julian Anastasov
2012-10-27 8:50 ` Eric Dumazet
2012-10-27 11:57 ` Eric Dumazet
2012-10-27 13:23 ` Julian Anastasov
2012-10-27 13:32 ` Eric Dumazet
2012-10-27 14:18 ` [PATCH net-next] tcp: better retrans tracking for defer-accept Eric Dumazet
2012-10-27 18:27 ` Neal Cardwell
2012-10-27 22:29 ` Julian Anastasov
2012-10-28 9:15 ` Eric Dumazet
2012-10-28 16:51 ` Julian Anastasov
2012-10-28 20:02 ` Eric Dumazet
2012-10-29 9:21 ` Julian Anastasov
2012-11-03 18:46 ` 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=1351238750-13611-1-git-send-email-subramanian.vijay@gmail.com \
--to=subramanian.vijay@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=enh@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=venkat.x.venkatsubra@oracle.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).