netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: menglong8.dong@gmail.com
To: edumazet@google.com
Cc: rostedt@goodmis.org, mingo@redhat.com, davem@davemloft.net,
	yoshfuji@linux-ipv6.org, dsahern@kernel.org, kuba@kernel.org,
	pabeni@redhat.com, imagedong@tencent.com, kafai@fb.com,
	talalahmad@google.com, keescook@chromium.org,
	dongli.zhang@oracle.com, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org
Subject: [PATCH net-next v3 9/9] net: tcp: use LINUX_MIB_TCPABORTONLINGER in tcp_rcv_state_process()
Date: Fri, 10 Jun 2022 11:42:04 +0800	[thread overview]
Message-ID: <20220610034204.67901-10-imagedong@tencent.com> (raw)
In-Reply-To: <20220610034204.67901-1-imagedong@tencent.com>

From: Menglong Dong <imagedong@tencent.com>

The statistics for 'tp->linger2 < 0' in tcp_rcv_state_process() seems
more accurate to be LINUX_MIB_TCPABORTONLINGER.

Signed-off-by: Menglong Dong <imagedong@tencent.com>
---
 net/ipv4/tcp_input.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/net/ipv4/tcp_input.c b/net/ipv4/tcp_input.c
index 9b9247b34a6c..07b06c12fe87 100644
--- a/net/ipv4/tcp_input.c
+++ b/net/ipv4/tcp_input.c
@@ -6592,7 +6592,7 @@ enum skb_drop_reason tcp_rcv_state_process(struct sock *sk, struct sk_buff *skb)
 
 		if (tp->linger2 < 0) {
 			tcp_done(sk);
-			NET_INC_STATS(sock_net(sk), LINUX_MIB_TCPABORTONDATA);
+			NET_INC_STATS(sock_net(sk), LINUX_MIB_TCPABORTONLINGER);
 			return SKB_DROP_REASON_TCP_LINGER;
 		}
 		if (TCP_SKB_CB(skb)->end_seq != TCP_SKB_CB(skb)->seq &&
-- 
2.36.1


      parent reply	other threads:[~2022-06-10  3:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10  3:41 [PATCH net-next v3 0/9] net: tcp: add skb drop reasons to tcp state change menglong8.dong
2022-06-10  3:41 ` [PATCH net-next v3 1/9] net: skb: introduce __skb_queue_purge_reason() menglong8.dong
2022-06-10  3:41 ` [PATCH net-next v3 2/9] net: sock: introduce sk_stream_kill_queues_reason() menglong8.dong
2022-06-10  3:41 ` [PATCH net-next v3 3/9] net: inet: add skb drop reason to inet_csk_destroy_sock() menglong8.dong
2022-06-10  3:41 ` [PATCH net-next v3 4/9] net: tcp: make tcp_rcv_synsent_state_process() return drop reasons menglong8.dong
2022-06-10  3:42 ` [PATCH net-next v3 5/9] net: tcp: make tcp_rcv_state_process() return drop reason menglong8.dong
2022-06-10  8:56   ` Eric Dumazet
2022-06-13  2:43     ` Menglong Dong
2022-06-10  3:42 ` [PATCH net-next v3 6/9] net: tcp: add skb drop reasons to tcp connect requesting menglong8.dong
2022-06-10  3:42 ` [PATCH net-next v3 7/9] net: tcp: add skb drop reasons to tcp tw code path menglong8.dong
2022-06-10  9:04   ` Eric Dumazet
2022-06-13  2:41     ` Menglong Dong
2022-06-10  3:42 ` [PATCH net-next v3 8/9] net: tcp: add skb drop reasons to route_req() menglong8.dong
2022-06-10  3:42 ` menglong8.dong [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=20220610034204.67901-10-imagedong@tencent.com \
    --to=menglong8.dong@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dongli.zhang@oracle.com \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=imagedong@tencent.com \
    --cc=kafai@fb.com \
    --cc=keescook@chromium.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=talalahmad@google.com \
    --cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).