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, edumazet@google.com,
matthieu.baerts@tessares.net, mptcp@lists.linux.dev
Subject: Re: [PATCH net-next 0/4] mptcp: Miscellaneous fixes and a new test case
Date: Fri, 20 May 2022 03:10:11 +0000 [thread overview]
Message-ID: <165301621191.9219.12868236037552729726.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220518220446.209750-1-mathew.j.martineau@linux.intel.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 18 May 2022 15:04:42 -0700 you wrote:
> Patches 1 and 3 remove helpers that were iterating over the subflow
> connection list without proper locking. Iteration was not needed in
> either case.
>
> Patch 2 fixes handling of MP_FAIL timeout, checking for orphaned
> subflows instead of using the MPTCP socket data lock and connection
> state.
>
> [...]
Here is the summary with links:
- [net-next,1/4] mptcp: stop using the mptcp_has_another_subflow() helper
https://git.kernel.org/netdev/net-next/c/7b16871f9932
- [net-next,2/4] mptcp: Check for orphaned subflow before handling MP_FAIL timer
https://git.kernel.org/netdev/net-next/c/d42f9e4e2384
- [net-next,3/4] mptcp: Do not traverse the subflow connection list without lock
https://git.kernel.org/netdev/net-next/c/d9fb797046c5
- [net-next,4/4] selftests: mptcp: add MP_FAIL reset testcase
https://git.kernel.org/netdev/net-next/c/2ba18161d407
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-05-20 3:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 22:04 [PATCH net-next 0/4] mptcp: Miscellaneous fixes and a new test case Mat Martineau
2022-05-18 22:04 ` [PATCH net-next 1/4] mptcp: stop using the mptcp_has_another_subflow() helper Mat Martineau
2022-05-18 22:04 ` [PATCH net-next 2/4] mptcp: Check for orphaned subflow before handling MP_FAIL timer Mat Martineau
2022-05-18 22:04 ` [PATCH net-next 3/4] mptcp: Do not traverse the subflow connection list without lock Mat Martineau
2022-05-18 22:04 ` [PATCH net-next 4/4] selftests: mptcp: add MP_FAIL reset testcase Mat Martineau
2022-05-20 3:10 ` 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=165301621191.9219.12868236037552729726.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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