public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts (NGI0) <matttbe@kernel.org>
Cc: mptcp@lists.linux.dev, martineau@kernel.org, geliang@kernel.org,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, kishen.maloor@intel.com, fw@strlen.de,
	peter.krystad@linux.intel.com, dmytro@shytyi.net,
	benjamin.hesmans@tessares.net, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, cpaasch@apple.com,
	stable@vger.kernel.org,
	syzbot+c53d4d3ddb327e80bc51@syzkaller.appspotmail.com
Subject: Re: [PATCH net 0/7] mptcp: locking cleanup & misc. fixes
Date: Mon, 12 Feb 2024 10:10:25 +0000	[thread overview]
Message-ID: <170773262501.4204.5549923375471395183.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240208-upstream-net-20240202-locking-cleanup-misc-v1-0-f75cc5b97e5a@kernel.org>

Hello:

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

On Thu, 08 Feb 2024 19:03:48 +0100 you wrote:
> Patches 1-4 are fixes for issues found by Paolo while working on adding
> TCP_NOTSENT_LOWAT support. The latter will need to track more states
> under the msk data lock. Since the locking msk locking schema is already
> quite complex, do a long awaited clean-up step by moving several
> confusing lockless initialization under the relevant locks. Note that it
> is unlikely a real race could happen even prior to such patches as the
> MPTCP-level state machine implicitly ensures proper serialization of the
> write accesses, even lacking explicit lock. But still, simplification is
> welcome and this will help for the maintenance. This can be backported
> up to v5.6.
> 
> [...]

Here is the summary with links:
  - [net,1/7] mptcp: drop the push_pending field
    https://git.kernel.org/netdev/net/c/bdd70eb68913
  - [net,2/7] mptcp: fix rcv space initialization
    https://git.kernel.org/netdev/net/c/013e3179dbd2
  - [net,3/7] mptcp: fix more tx path fields initialization
    https://git.kernel.org/netdev/net/c/3f83d8a77eee
  - [net,4/7] mptcp: corner case locking for rx path fields initialization
    https://git.kernel.org/netdev/net/c/e4a0fa47e816
  - [net,5/7] mptcp: check addrs list in userspace_pm_get_local_id
    https://git.kernel.org/netdev/net/c/f012d796a6de
  - [net,6/7] mptcp: really cope with fastopen race
    https://git.kernel.org/netdev/net/c/337cebbd850f
  - [net,7/7] MAINTAINERS: update Geliang's email address
    https://git.kernel.org/netdev/net/c/68990d006d42

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



      parent reply	other threads:[~2024-02-12 10:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-08 18:03 [PATCH net 0/7] mptcp: locking cleanup & misc. fixes Matthieu Baerts (NGI0)
2024-02-08 18:03 ` [PATCH net 1/7] mptcp: drop the push_pending field Matthieu Baerts (NGI0)
2024-02-08 18:03 ` [PATCH net 2/7] mptcp: fix rcv space initialization Matthieu Baerts (NGI0)
2024-02-08 18:03 ` [PATCH net 3/7] mptcp: fix more tx path fields initialization Matthieu Baerts (NGI0)
2024-02-08 18:03 ` [PATCH net 4/7] mptcp: corner case locking for rx " Matthieu Baerts (NGI0)
2024-02-08 18:03 ` [PATCH net 5/7] mptcp: check addrs list in userspace_pm_get_local_id Matthieu Baerts (NGI0)
2024-02-08 18:03 ` [PATCH net 6/7] mptcp: really cope with fastopen race Matthieu Baerts (NGI0)
2024-02-12 10: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=170773262501.4204.5549923375471395183.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=benjamin.hesmans@tessares.net \
    --cc=cpaasch@apple.com \
    --cc=davem@davemloft.net \
    --cc=dmytro@shytyi.net \
    --cc=edumazet@google.com \
    --cc=fw@strlen.de \
    --cc=geliang@kernel.org \
    --cc=kishen.maloor@intel.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martineau@kernel.org \
    --cc=matttbe@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=peter.krystad@linux.intel.com \
    --cc=stable@vger.kernel.org \
    --cc=syzbot+c53d4d3ddb327e80bc51@syzkaller.appspotmail.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