public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts <matttbe@kernel.org>
Cc: mptcp@lists.linux.dev, martineau@kernel.org, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	alexanderduyck@fb.com, geliang.tang@suse.com,
	psonparo@redhat.com, shuah@kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	cpaasch@apple.com, stable@vger.kernel.org,
	syzbot+9dfbaedb6e6baca57a32@syzkaller.appspotmail.com,
	xmu@redhat.com
Subject: Re: [PATCH net 0/5] mptcp: misc. fixes for v6.7
Date: Wed, 15 Nov 2023 04:20:23 +0000	[thread overview]
Message-ID: <170002202392.25123.5567569112552838973.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231114-upstream-net-20231113-mptcp-misc-fixes-6-7-rc2-v1-0-7b9cd6a7b7f4@kernel.org>

Hello:

This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Tue, 14 Nov 2023 00:16:12 +0100 you wrote:
> Here are a few fixes related to MPTCP:
> 
> - Patch 1 limits GSO max size to ~64K when MPTCP is being used due to a
>   spec limit. 'gso_max_size' can exceed the max value supported by MPTCP
>   since v5.19.
> 
> - Patch 2 fixes a possible NULL pointer dereference on close that can
>   happen since v6.7-rc1.
> 
> [...]

Here is the summary with links:
  - [net,1/5] mptcp: deal with large GSO size
    https://git.kernel.org/netdev/net/c/9fce92f050f4
  - [net,2/5] mptcp: fix possible NULL pointer dereference on close
    https://git.kernel.org/netdev/net/c/d109a7767273
  - [net,3/5] mptcp: add validity check for sending RM_ADDR
    https://git.kernel.org/netdev/net/c/8df220b29282
  - [net,4/5] mptcp: fix setsockopt(IP_TOS) subflow locking
    https://git.kernel.org/netdev/net/c/7679d34f97b7
  - [net,5/5] selftests: mptcp: fix fastclose with csum failure
    https://git.kernel.org/netdev/net/c/7cefbe5e1dac

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-11-15  4:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-13 23:16 [PATCH net 0/5] mptcp: misc. fixes for v6.7 Matthieu Baerts
2023-11-13 23:16 ` [PATCH net 1/5] mptcp: deal with large GSO size Matthieu Baerts
2023-11-13 23:16 ` [PATCH net 2/5] mptcp: fix possible NULL pointer dereference on close Matthieu Baerts
2023-11-13 23:16 ` [PATCH net 3/5] mptcp: add validity check for sending RM_ADDR Matthieu Baerts
2023-11-13 23:16 ` [PATCH net 4/5] mptcp: fix setsockopt(IP_TOS) subflow locking Matthieu Baerts
2023-11-13 23:16 ` [PATCH net 5/5] selftests: mptcp: fix fastclose with csum failure Matthieu Baerts
2023-11-15  4: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=170002202392.25123.5567569112552838973.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexanderduyck@fb.com \
    --cc=cpaasch@apple.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=geliang.tang@suse.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@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=psonparo@redhat.com \
    --cc=shuah@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=syzbot+9dfbaedb6e6baca57a32@syzkaller.appspotmail.com \
    --cc=xmu@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