From: Jakub Kicinski <kuba@kernel•org>
To: Jason Xing <kerneljasonxing@gmail•com>
Cc: davem@davemloft•net, edumazet@google•com, pabeni@redhat•com,
dsahern@kernel•org, kuniyu@amazon•com, netdev@vger•kernel.org,
Jason Xing <kernelxing@tencent•com>
Subject: Re: [PATCH net-next v4 0/7] tcp: completely support active reset
Date: Fri, 2 Aug 2024 08:30:12 -0700 [thread overview]
Message-ID: <20240802083012.062e2c0e@kernel.org> (raw)
In-Reply-To: <20240802102112.9199-1-kerneljasonxing@gmail.com>
On Fri, 2 Aug 2024 18:21:05 +0800 Jason Xing wrote:
> 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).
What happened to waiting 24h before posting the next version? :|
--
pv-bot: 24h
next prev parent reply other threads:[~2024-08-02 15:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 10:21 [PATCH net-next v4 0/7] tcp: completely support active reset Jason Xing
2024-08-02 10:21 ` [PATCH net-next v4 1/7] tcp: rstreason: introduce SK_RST_REASON_TCP_ABORT_ON_CLOSE for " Jason Xing
2024-08-02 10:21 ` [PATCH net-next v4 2/7] tcp: rstreason: introduce SK_RST_REASON_TCP_ABORT_ON_LINGER " Jason Xing
2024-08-02 10:21 ` [PATCH net-next v4 3/7] tcp: rstreason: introduce SK_RST_REASON_TCP_ABORT_ON_MEMORY " Jason Xing
2024-08-02 10:21 ` [PATCH net-next v4 4/7] tcp: rstreason: introduce SK_RST_REASON_TCP_STATE " Jason Xing
2024-08-02 10:21 ` [PATCH net-next v4 5/7] tcp: rstreason: introduce SK_RST_REASON_TCP_KEEPALIVE_TIMEOUT " Jason Xing
2024-08-02 10:21 ` [PATCH net-next v4 6/7] tcp: rstreason: introduce SK_RST_REASON_TCP_DISCONNECT_WITH_DATA " Jason Xing
2024-08-02 10:21 ` [PATCH net-next v4 7/7] tcp: rstreason: let it work finally in tcp_send_active_reset() Jason Xing
2024-08-02 15:30 ` Jakub Kicinski [this message]
2024-08-02 17:43 ` [PATCH net-next v4 0/7] tcp: completely support active reset Jason Xing
2024-08-07 9:30 ` patchwork-bot+netdevbpf
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=20240802083012.062e2c0e@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=dsahern@kernel$(echo .)org \
--cc=edumazet@google$(echo .)com \
--cc=kerneljasonxing@gmail$(echo .)com \
--cc=kernelxing@tencent$(echo .)com \
--cc=kuniyu@amazon$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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