From: Jason Xing <kerneljasonxing@gmail.com>
To: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, dsahern@kernel.org, kuniyu@amazon.com
Cc: netdev@vger.kernel.org, Jason Xing <kernelxing@tencent.com>
Subject: [PATCH net-next v2 0/6] tcp: completely support active reset
Date: Wed, 31 Jul 2024 20:09:49 +0800 [thread overview]
Message-ID: <20240731120955.23542-1-kerneljasonxing@gmail.com> (raw)
From: Jason Xing <kernelxing@tencent.com>
This time the patch series finally covers all the cases in the active
reset logic. After this, we can know the related exact reason(s).
v2
Link: https://lore.kernel.org/all/20240730133513.99986-1-kerneljasonxing@gmail.com/
1. use RFC 9293 in the comment and changelog instead of old RFC 793
2. correct the comment and changelog in patch 5
Jason Xing (6):
tcp: rstreason: introduce SK_RST_REASON_TCP_ABORT_ON_CLOSE for active
reset
tcp: rstreason: introduce SK_RST_REASON_TCP_ABORT_ON_LINGER for active
reset
tcp: rstreason: introduce SK_RST_REASON_TCP_ABORT_ON_MEMORY for active
reset
tcp: rstreason: introduce SK_RST_REASON_TCP_STATE for active reset
tcp: rstreason: introduce SK_RST_REASON_TCP_TIMEOUT for active reset
tcp: rstreason: let it work finally in tcp_send_active_reset()
include/net/rstreason.h | 32 ++++++++++++++++++++++++++++++++
net/ipv4/tcp.c | 10 +++++-----
net/ipv4/tcp_output.c | 2 +-
net/ipv4/tcp_timer.c | 6 +++---
4 files changed, 41 insertions(+), 9 deletions(-)
--
2.37.3
next reply other threads:[~2024-07-31 12:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 12:09 Jason Xing [this message]
2024-07-31 12:09 ` [PATCH net-next v2 1/6] tcp: rstreason: introduce SK_RST_REASON_TCP_ABORT_ON_CLOSE for active reset Jason Xing
2024-08-01 6:47 ` Eric Dumazet
2024-07-31 12:09 ` [PATCH net-next v2 2/6] tcp: rstreason: introduce SK_RST_REASON_TCP_ABORT_ON_LINGER " Jason Xing
2024-08-01 6:48 ` Eric Dumazet
2024-07-31 12:09 ` [PATCH net-next v2 3/6] tcp: rstreason: introduce SK_RST_REASON_TCP_ABORT_ON_MEMORY " Jason Xing
2024-08-01 6:49 ` Eric Dumazet
2024-07-31 12:09 ` [PATCH net-next v2 4/6] tcp: rstreason: introduce SK_RST_REASON_TCP_STATE " Jason Xing
2024-08-01 6:56 ` Eric Dumazet
2024-08-01 9:51 ` Jason Xing
2024-08-01 10:06 ` Eric Dumazet
2024-08-01 10:24 ` Jason Xing
2024-07-31 12:09 ` [PATCH net-next v2 5/6] tcp: rstreason: introduce SK_RST_REASON_TCP_TIMEOUT " Jason Xing
2024-08-01 6:58 ` Eric Dumazet
2024-08-01 9:30 ` Jason Xing
2024-07-31 12:09 ` [PATCH net-next v2 6/6] tcp: rstreason: let it work finally in tcp_send_active_reset() 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=20240731120955.23542-1-kerneljasonxing@gmail.com \
--to=kerneljasonxing@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kernelxing@tencent.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--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).