From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <kerneljasonxing@gmail.com>
Cc: <davem@davemloft.net>, <dsahern@kernel.org>,
<edumazet@google.com>, <kernelxing@tencent.com>,
<kuba@kernel.org>, <kuniyu@amazon.com>, <netdev@vger.kernel.org>,
<pabeni@redhat.com>
Subject: Re: [PATCH net-next v6 06/11] tcp: introduce dropreasons in receive path
Date: Sun, 18 Feb 2024 20:47:44 -0800 [thread overview]
Message-ID: <20240219044744.99367-1-kuniyu@amazon.com> (raw)
In-Reply-To: <20240219032838.91723-7-kerneljasonxing@gmail.com>
From: Jason Xing <kerneljasonxing@gmail.com>
Date: Mon, 19 Feb 2024 11:28:33 +0800
> From: Jason Xing <kernelxing@tencent.com>
>
> Soon later patches can use these relatively more accurate
> reasons to recognise and find out the cause.
>
> Signed-off-by: Jason Xing <kernelxing@tencent.com>
> --
> v5:
> Link: https://lore.kernel.org/netdev/3a495358-4c47-4a9f-b116-5f9c8b44e5ab@kernel.org/
> 1. Use new name (TCP_ABORT_ON_DATA) for readability (David)
> 2. change the title of this patch
> ---
> include/net/dropreason-core.h | 15 ++++++++++++++-
> 1 file changed, 14 insertions(+), 1 deletion(-)
>
> diff --git a/include/net/dropreason-core.h b/include/net/dropreason-core.h
> index 3c867384dead..402367bfa56f 100644
> --- a/include/net/dropreason-core.h
> +++ b/include/net/dropreason-core.h
> @@ -30,6 +30,7 @@
> FN(TCP_AOFAILURE) \
> FN(SOCKET_BACKLOG) \
> FN(TCP_FLAGS) \
> + FN(TCP_ABORT_ON_DATA) \
> FN(TCP_ZEROWINDOW) \
> FN(TCP_OLD_DATA) \
> FN(TCP_OVERWINDOW) \
> @@ -37,6 +38,7 @@
> FN(TCP_RFC7323_PAWS) \
> FN(TCP_OLD_SEQUENCE) \
> FN(TCP_INVALID_SEQUENCE) \
> + FN(TCP_INVALID_ACK_SEQUENCE) \
> FN(TCP_RESET) \
> FN(TCP_INVALID_SYN) \
> FN(TCP_CLOSE) \
> @@ -204,6 +206,11 @@ enum skb_drop_reason {
> SKB_DROP_REASON_SOCKET_BACKLOG,
> /** @SKB_DROP_REASON_TCP_FLAGS: TCP flags invalid */
> SKB_DROP_REASON_TCP_FLAGS,
> + /**
> + * @SKB_DROP_REASON_TCP_ABORT_ON_DATA: abort on data, corresponding to
> + * LINUX_MIB_TCPABORTONDATA
> + */
> + SKB_DROP_REASON_TCP_ABORT_ON_DATA,
> /**
> * @SKB_DROP_REASON_TCP_ZEROWINDOW: TCP receive window size is zero,
> * see LINUX_MIB_TCPZEROWINDOWDROP
> @@ -228,13 +235,19 @@ enum skb_drop_reason {
> SKB_DROP_REASON_TCP_OFOMERGE,
> /**
> * @SKB_DROP_REASON_TCP_RFC7323_PAWS: PAWS check, corresponding to
> - * LINUX_MIB_PAWSESTABREJECTED
> + * LINUX_MIB_PAWSESTABREJECTED, LINUX_MIB_PAWSACTIVEREJECTED
> */
> SKB_DROP_REASON_TCP_RFC7323_PAWS,
> /** @SKB_DROP_REASON_TCP_OLD_SEQUENCE: Old SEQ field (duplicate packet) */
> SKB_DROP_REASON_TCP_OLD_SEQUENCE,
> /** @SKB_DROP_REASON_TCP_INVALID_SEQUENCE: Not acceptable SEQ field */
> SKB_DROP_REASON_TCP_INVALID_SEQUENCE,
> + /**
> + * @SKB_DROP_REASON_TCP_INVALID_ACK_SEQUENCE: Not acceptable ACK SEQ
> + * field. because of ack sequence is not in the window between snd_una
nit: s/. because of/ because/
> + * and snd_nxt
> + */
> + SKB_DROP_REASON_TCP_INVALID_ACK_SEQUENCE,
> /** @SKB_DROP_REASON_TCP_RESET: Invalid RST packet */
> SKB_DROP_REASON_TCP_RESET,
> /**
> --
> 2.37.3
>
next prev parent reply other threads:[~2024-02-19 4:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 3:28 [PATCH net-next v6 00/11] introduce drop reasons for tcp receive path Jason Xing
2024-02-19 3:28 ` [PATCH net-next v6 01/11] tcp: add a dropreason definitions and prepare for cookie check Jason Xing
2024-02-19 4:06 ` Kuniyuki Iwashima
2024-02-19 4:56 ` Jason Xing
2024-02-19 3:28 ` [PATCH net-next v6 02/11] tcp: directly drop skb in cookie check for ipv4 Jason Xing
2024-02-19 4:13 ` Kuniyuki Iwashima
2024-02-19 3:28 ` [PATCH net-next v6 03/11] tcp: use drop reasons " Jason Xing
2024-02-19 3:28 ` [PATCH net-next v6 04/11] tcp: directly drop skb in cookie check for ipv6 Jason Xing
2024-02-19 4:38 ` Kuniyuki Iwashima
2024-02-19 4:57 ` Jason Xing
2024-02-19 3:28 ` [PATCH net-next v6 05/11] tcp: use drop reasons " Jason Xing
2024-02-19 3:28 ` [PATCH net-next v6 06/11] tcp: introduce dropreasons in receive path Jason Xing
2024-02-19 4:47 ` Kuniyuki Iwashima [this message]
2024-02-19 4:57 ` Jason Xing
2024-02-19 3:28 ` [PATCH net-next v6 07/11] tcp: add more specific possible drop reasons in tcp_rcv_synsent_state_process() Jason Xing
2024-02-19 4:54 ` Kuniyuki Iwashima
2024-02-19 5:07 ` Jason Xing
2024-02-19 3:28 ` [PATCH net-next v6 08/11] tcp: add dropreasons in tcp_rcv_state_process() Jason Xing
2024-02-19 3:28 ` [PATCH net-next v6 09/11] tcp: make the dropreason really work when calling tcp_rcv_state_process() Jason Xing
2024-02-19 3:28 ` [PATCH net-next v6 10/11] tcp: make dropreason in tcp_child_process() work Jason Xing
2024-02-19 3:28 ` [PATCH net-next v6 11/11] tcp: get rid of NOT_SPECIFIED reason in tcp_v4/6_do_rcv Jason Xing
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=20240219044744.99367-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kerneljasonxing@gmail.com \
--cc=kernelxing@tencent.com \
--cc=kuba@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).