[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240730200633.93761-1-kuniyu@amazon.com>
Date: Tue, 30 Jul 2024 13:06:33 -0700
From: Kuniyuki Iwashima <kuniyu@...zon.com>
To: <kerneljasonxing@...il.com>
CC: <davem@...emloft.net>, <dsahern@...nel.org>, <edumazet@...gle.com>,
<kernelxing@...cent.com>, <kuba@...nel.org>, <netdev@...r.kernel.org>,
<pabeni@...hat.com>, <kuniyu@...zon.com>
Subject: Re: [PATCH net-next 4/6] tcp: rstreason: introduce SK_RST_REASON_TCP_STATE for active reset
From: Jason Xing <kerneljasonxing@...il.com>
Date: Tue, 30 Jul 2024 21:35:11 +0800
> From: Jason Xing <kernelxing@...cent.com>
>
> Introducing a new type TCP_STATE to handle some reset conditions
> appearing in RFC 793 due to its socket state.
Why not RFC 9293 ?
Was there any discrepancy ?
>
> Signed-off-by: Jason Xing <kernelxing@...cent.com>
> ---
> include/net/rstreason.h | 6 ++++++
> net/ipv4/tcp.c | 4 ++--
> net/ipv4/tcp_timer.c | 2 +-
> 3 files changed, 9 insertions(+), 3 deletions(-)
>
> diff --git a/include/net/rstreason.h b/include/net/rstreason.h
> index eef658da8952..fecaa57f1634 100644
> --- a/include/net/rstreason.h
> +++ b/include/net/rstreason.h
> @@ -20,6 +20,7 @@
> FN(TCP_ABORT_ON_CLOSE) \
> FN(TCP_ABORT_ON_LINGER) \
> FN(TCP_ABORT_ON_MEMORY) \
> + FN(TCP_STATE) \
> FN(MPTCP_RST_EUNSPEC) \
> FN(MPTCP_RST_EMPTCP) \
> FN(MPTCP_RST_ERESOURCE) \
> @@ -102,6 +103,11 @@ enum sk_rst_reason {
> * corresponding to LINUX_MIB_TCPABORTONMEMORY
> */
> SK_RST_REASON_TCP_ABORT_ON_MEMORY,
> + /**
> + * @SK_RST_REASON_TCP_STATE: abort on tcp state
> + * Please see RFC 793 for all possible reset conditions
> + */
> + SK_RST_REASON_TCP_STATE,
Same here.
Powered by blists - more mailing lists