From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts <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, horms@kernel.org, corbet@lwn.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net 0/2] mptcp: blackhole only if 1st SYN retrans w/o MPC is accepted
Date: Thu, 30 Jan 2025 13:10:30 +0000 [thread overview]
Message-ID: <173824263075.953543.6219182517471965649.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250129-net-mptcp-blackhole-fix-v1-0-afe88e5a6d2c@kernel.org>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 29 Jan 2025 13:24:31 +0100 you wrote:
> Here are two small fixes for issues introduced in v6.12.
>
> - Patch 1: reset the mpc_drop mark for other SYN retransmits, to only
> consider an MPTCP blackhole when the first SYN retransmitted without
> the MPTCP options is accepted, as initially intended.
>
> - Patch 2: also mention in the doc that the blackhole_timeout sysctl
> knob is per-netns, like all the others.
>
> [...]
Here is the summary with links:
- [net,1/2] mptcp: blackhole only if 1st SYN retrans w/o MPC is accepted
https://git.kernel.org/netdev/net/c/e598d8981fd3
- [net,2/2] doc: mptcp: sysctl: blackhole_timeout is per-netns
https://git.kernel.org/netdev/net/c/18da4b5d1232
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:[~2025-01-30 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 12:24 Matthieu Baerts (NGI0)
2025-01-29 12:24 ` [PATCH net 1/2] " Matthieu Baerts (NGI0)
2025-01-29 12:24 ` [PATCH net 2/2] doc: mptcp: sysctl: blackhole_timeout is per-netns Matthieu Baerts (NGI0)
2025-01-30 13: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=173824263075.953543.6219182517471965649.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.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=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
all inboxes | Powered by JetHome®