From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: dcaratti@redhat.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, mathew.j.martineau@linux.intel.com,
mengensun@tencent.com, imagedong@tencent.com, pabeni@redhat.com,
benbjiang@tencent.com, linux-kernel@vger.kernel.org,
mptcp@lists.linux.dev, netdev@vger.kernel.org
Subject: Re: [PATCH net 0/2] mptcp: More fixes for 6.1
Date: Tue, 29 Nov 2022 02:20:16 +0000 [thread overview]
Message-ID: <166968841676.21086.3587694150768169897.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221128154239.1999234-1-matthieu.baerts@tessares.net>
Hello:
This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 28 Nov 2022 16:42:36 +0100 you wrote:
> Patch 1 makes sure data received after a close will still be processed and acked
> as exepected. This is a regression for a commit introduced in v5.11.
>
> Patch 2 fixes a kernel deadlock found when working on validating TFO with a
> listener MPTCP socket. This is not directly linked to TFO but it is easier to
> reproduce the issue with it. This fixes a bug introduced by a commit from v6.0.
>
> [...]
Here is the summary with links:
- [net,1/2] mptcp: don't orphan ssk in mptcp_close()
https://git.kernel.org/netdev/net/c/fe94800184f2
- [net,2/2] mptcp: fix sleep in atomic at close time
https://git.kernel.org/netdev/net/c/b4f166651d03
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-11-29 2:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 15:42 [PATCH net 0/2] mptcp: More fixes for 6.1 Matthieu Baerts
2022-11-28 15:42 ` [PATCH net 1/2] mptcp: don't orphan ssk in mptcp_close() Matthieu Baerts
2022-11-28 15:42 ` [PATCH net 2/2] mptcp: fix sleep in atomic at close time Matthieu Baerts
2022-11-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=166968841676.21086.3587694150768169897.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=benbjiang@tencent.com \
--cc=davem@davemloft.net \
--cc=dcaratti@redhat.com \
--cc=edumazet@google.com \
--cc=imagedong@tencent.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathew.j.martineau@linux.intel.com \
--cc=matthieu.baerts@tessares.net \
--cc=mengensun@tencent.com \
--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;
as well as URLs for NNTP newsgroup(s).