From: patchwork-bot+netdevbpf@kernel.org
To: Mat Martineau <mathew.j.martineau@linux.intel.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, matthieu.baerts@tessares.net,
mptcp@lists.linux.dev
Subject: Re: [PATCH net-next 0/7] mptcp: Timeout for MP_FAIL response
Date: Wed, 27 Apr 2022 09:50:12 +0000 [thread overview]
Message-ID: <165105301244.17866.15528494250616223898.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220426215717.129506-1-mathew.j.martineau@linux.intel.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Tue, 26 Apr 2022 14:57:10 -0700 you wrote:
> When one peer sends an infinite mapping to coordinate fallback from
> MPTCP to regular TCP, the other peer is expected to send a packet with
> the MPTCP MP_FAIL option to acknowledge the infinite mapping. Rather
> than leave the connection in some half-fallback state, this series adds
> a timeout after which the infinite mapping sender will reset the
> connection.
>
> [...]
Here is the summary with links:
- [net-next,1/7] selftests: mptcp: add infinite map testcase
https://git.kernel.org/netdev/net-next/c/b6e074e171bc
- [net-next,2/7] mptcp: use mptcp_stop_timer
https://git.kernel.org/netdev/net-next/c/bcf3cf93f645
- [net-next,3/7] mptcp: add data lock for sk timers
https://git.kernel.org/netdev/net-next/c/4293248c6704
- [net-next,4/7] mptcp: add MP_FAIL response support
https://git.kernel.org/netdev/net-next/c/9c81be0dbc89
- [net-next,5/7] mptcp: reset subflow when MP_FAIL doesn't respond
https://git.kernel.org/netdev/net-next/c/49fa1919d6bc
- [net-next,6/7] selftests: mptcp: check MP_FAIL response mibs
https://git.kernel.org/netdev/net-next/c/1f7d325f7d49
- [net-next,7/7] selftests: mptcp: print extra msg in chk_csum_nr
https://git.kernel.org/netdev/net-next/c/53f368bfff31
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-04-27 9:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 21:57 [PATCH net-next 0/7] mptcp: Timeout for MP_FAIL response Mat Martineau
2022-04-26 21:57 ` [PATCH net-next 1/7] selftests: mptcp: add infinite map testcase Mat Martineau
2022-04-26 21:57 ` [PATCH net-next 2/7] mptcp: use mptcp_stop_timer Mat Martineau
2022-04-26 21:57 ` [PATCH net-next 3/7] mptcp: add data lock for sk timers Mat Martineau
2022-04-26 21:57 ` [PATCH net-next 4/7] mptcp: add MP_FAIL response support Mat Martineau
2022-04-26 21:57 ` [PATCH net-next 5/7] mptcp: reset subflow when MP_FAIL doesn't respond Mat Martineau
2022-04-26 21:57 ` [PATCH net-next 6/7] selftests: mptcp: check MP_FAIL response mibs Mat Martineau
2022-04-26 21:57 ` [PATCH net-next 7/7] selftests: mptcp: print extra msg in chk_csum_nr Mat Martineau
2022-04-27 9:50 ` patchwork-bot+netdevbpf [this message]
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=165105301244.17866.15528494250616223898.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=mathew.j.martineau@linux.intel.com \
--cc=matthieu.baerts@tessares.net \
--cc=mptcp@lists.linux.dev \
--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