Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: mptcp@lists.linux.dev, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, dcaratti@redhat.com,
	mathew.j.martineau@linux.intel.com,
	benjamin.hesmans@tessares.net, geliangtang@gmail.com,
	shuah@kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH net 0/6] mptcp: fixes for v6.2
Date: Wed, 08 Feb 2023 09:40:18 +0000	[thread overview]
Message-ID: <167584921886.28651.15884792835750696627.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230207-upstream-net-20230207-various-fix-6-2-v1-0-2031b495c7cc@tessares.net>

Hello:

This series was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:

On Tue, 07 Feb 2023 14:04:12 +0100 you wrote:
> Patch 1 clears resources earlier if there is no more reasons to keep
> MPTCP sockets alive.
> 
> Patches 2 and 3 fix some locking issues visible in some rare corner
> cases: the linked issues should be quite hard to reproduce.
> 
> Patch 4 makes sure subflows are correctly cleaned after the end of a
> connection.
> 
> [...]

Here is the summary with links:
  - [net,1/6] mptcp: do not wait for bare sockets' timeout
    https://git.kernel.org/netdev/net/c/d4e85922e3e7
  - [net,2/6] mptcp: fix locking for setsockopt corner-case
    https://git.kernel.org/netdev/net/c/21e43569685d
  - [net,3/6] mptcp: fix locking for in-kernel listener creation
    https://git.kernel.org/netdev/net/c/ad2171009d96
  - [net,4/6] mptcp: be careful on subflow status propagation on errors
    https://git.kernel.org/netdev/net/c/1249db44a102
  - [net,5/6] selftests: mptcp: allow more slack for slow test-case
    https://git.kernel.org/netdev/net/c/a635a8c3df66
  - [net,6/6] selftests: mptcp: stop tests earlier
    https://git.kernel.org/netdev/net/c/070d6dafacba

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-02-08  9:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-07 13:04 [PATCH net 0/6] mptcp: fixes for v6.2 Matthieu Baerts
2023-02-07 13:04 ` [PATCH net 1/6] mptcp: do not wait for bare sockets' timeout Matthieu Baerts
2023-02-07 13:04 ` [PATCH net 2/6] mptcp: fix locking for setsockopt corner-case Matthieu Baerts
2023-02-07 13:04 ` [PATCH net 3/6] mptcp: fix locking for in-kernel listener creation Matthieu Baerts
2023-02-07 13:04 ` [PATCH net 4/6] mptcp: be careful on subflow status propagation on errors Matthieu Baerts
2023-02-07 13:04 ` [PATCH net 5/6] selftests: mptcp: allow more slack for slow test-case Matthieu Baerts
2023-02-07 13:04 ` [PATCH net 6/6] selftests: mptcp: stop tests earlier Matthieu Baerts
2023-02-08  9:40 ` 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=167584921886.28651.15884792835750696627.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=benjamin.hesmans@tessares.net \
    --cc=davem@davemloft.net \
    --cc=dcaratti@redhat.com \
    --cc=edumazet@google.com \
    --cc=geliangtang@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.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 \
    --cc=shuah@kernel.org \
    --cc=stable@vger.kernel.org \
    /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