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, fw@strlen.de, dcaratti@redhat.com,
mptcp@lists.linux.dev
Subject: Re: [PATCH net 0/3] mptcp: Fixes for mptcp cleanup/close and a selftest
Date: Fri, 05 Aug 2022 08:00:14 +0000 [thread overview]
Message-ID: <165968641473.31624.9455539276558516892.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220805002127.88430-1-mathew.j.martineau@linux.intel.com>
Hello:
This series was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 4 Aug 2022 17:21:24 -0700 you wrote:
> Patch 1 fixes an issue with leaking subflow sockets if there's a failure
> in a CGROUP_INET_SOCK_CREATE eBPF program.
>
> Patch 2 fixes a syzkaller-detected race at MPTCP socket close.
>
> Patch 3 is a fix for one mode of the mptcp_connect.sh selftest.
>
> [...]
Here is the summary with links:
- [net,1/3] mptcp: move subflow cleanup in mptcp_destroy_common()
https://git.kernel.org/netdev/net/c/c0bf3c6aa444
- [net,2/3] mptcp: do not queue data on closed subflows
https://git.kernel.org/netdev/net/c/c886d70286bf
- [net,3/3] selftests: mptcp: make sendfile selftest work
https://git.kernel.org/netdev/net/c/df9e03aec3b1
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-08-05 8:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 0:21 [PATCH net 0/3] mptcp: Fixes for mptcp cleanup/close and a selftest Mat Martineau
2022-08-05 0:21 ` [PATCH net 1/3] mptcp: move subflow cleanup in mptcp_destroy_common() Mat Martineau
2022-08-05 0:21 ` [PATCH net 2/3] mptcp: do not queue data on closed subflows Mat Martineau
2022-08-05 0:21 ` [PATCH net 3/3] selftests: mptcp: make sendfile selftest work Mat Martineau
2022-08-05 8:00 ` 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=165968641473.31624.9455539276558516892.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dcaratti@redhat.com \
--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