[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<171258122800.2224.8882516894860681833.git-patchwork-notify@kernel.org>
Date: Mon, 08 Apr 2024 13:00:28 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Jason Xing <kerneljasonxing@...il.com>
Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, matttbe@...nel.org, martineau@...nel.org,
geliang@...nel.org, mptcp@...ts.linux.dev, netdev@...r.kernel.org,
kernelxing@...cent.com
Subject: Re: [PATCH net-next v2] mptcp: add reset reason options in some places
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@...emloft.net>:
On Sat, 6 Apr 2024 09:48:48 +0800 you wrote:
> From: Jason Xing <kernelxing@...cent.com>
>
> The reason codes are handled in two ways nowadays (quoting Mat Martineau):
> 1. Sending in the MPTCP option on RST packets when there is no subflow
> context available (these use subflow_add_reset_reason() and directly call
> a TCP-level send_reset function)
> 2. The "normal" way via subflow->reset_reason. This will propagate to both
> the outgoing reset packet and to a local path manager process via netlink
> in mptcp_event_sub_closed()
>
> [...]
Here is the summary with links:
- [net-next,v2] mptcp: add reset reason options in some places
https://git.kernel.org/netdev/net-next/c/382c60019ee7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists