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, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net 0/2] mptcp: fix duplicate data handling
Date: Thu, 01 Aug 2024 10:40:33 +0000 [thread overview]
Message-ID: <172250883325.19369.10430286155918787795.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240731-upstream-net-20240731-mptcp-dup-data-v1-0-bde833fa628a@kernel.org>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 31 Jul 2024 12:10:13 +0200 you wrote:
> In some cases, the subflow-level's copied_seq counter was incorrectly
> increased, leading to an unexpected subflow reset.
>
> Patch 1/2 fixes the RCVPRUNED MIB counter that was attached to the wrong
> event since its introduction in v5.14, backported to v5.11.
>
> Patch 2/2 fixes the copied_seq counter issues, is present since v5.10.
>
> [...]
Here is the summary with links:
- [net,1/2] mptcp: fix bad RCVPRUNED mib accounting
https://git.kernel.org/netdev/net/c/0a567c2a1003
- [net,2/2] mptcp: fix duplicate data handling
https://git.kernel.org/netdev/net/c/68cc924729ff
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:[~2024-08-01 10:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 10:10 [PATCH net 0/2] mptcp: fix duplicate data handling Matthieu Baerts (NGI0)
2024-07-31 10:10 ` [PATCH net 1/2] mptcp: fix bad RCVPRUNED mib accounting Matthieu Baerts (NGI0)
2024-07-31 10:10 ` [PATCH net 2/2] mptcp: fix duplicate data handling Matthieu Baerts (NGI0)
2024-08-01 10: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=172250883325.19369.10430286155918787795.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--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=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