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, fw@strlen.de,
matthieu.baerts@tessares.net, mptcp@lists.linux.dev
Subject: Re: [PATCH net 0/2] mptcp: Properly clean up unaccepted subflows
Date: Thu, 29 Sep 2022 02:20:17 +0000 [thread overview]
Message-ID: <166441801752.18961.14079404286061785586.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220927193158.195729-1-mathew.j.martineau@linux.intel.com>
Hello:
This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 27 Sep 2022 12:31:56 -0700 you wrote:
> Patch 1 factors out part of the mptcp_close() function for use by a caller
> that already owns the socket lock. This is a prerequisite for patch 2.
>
> Patch 2 is the fix that fully cleans up the unaccepted subflow sockets.
>
> Menglong Dong (2):
> mptcp: factor out __mptcp_close() without socket lock
> mptcp: fix unreleased socket in accept queue
>
> [...]
Here is the summary with links:
- [net,1/2] mptcp: factor out __mptcp_close() without socket lock
https://git.kernel.org/netdev/net/c/26d3e21ce1aa
- [net,2/2] mptcp: fix unreleased socket in accept queue
https://git.kernel.org/netdev/net/c/30e51b923e43
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-09-29 2:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 19:31 [PATCH net 0/2] mptcp: Properly clean up unaccepted subflows Mat Martineau
2022-09-27 19:31 ` [PATCH net 1/2] mptcp: factor out __mptcp_close() without socket lock Mat Martineau
2022-09-27 19:31 ` [PATCH net 2/2] mptcp: fix unreleased socket in accept queue Mat Martineau
2022-09-29 2:20 ` 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=166441801752.18961.14079404286061785586.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--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