From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
matttbe@kernel.org, martineau@kernel.org, geliang@kernel.org,
horms@kernel.org, kuniyu@google.com, netdev@vger.kernel.org,
kylebot@openai.com
Subject: Re: [PATCH net] mptcp: reject DATA_ACKs against a reversed send interval
Date: Tue, 10 Nov 2026 19:50:04 +0000 [thread overview]
Message-ID: <179434020493.26472.7236408102827538052.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261104130747.1045741-1-edumazet@kernel.org>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 4 Nov 2026 14:07:47 +0100 you wrote:
> From: Kyle Zeng <kylebot@openai.com>
>
> ack_update_msk() samples snd_nxt before taking the data lock, but reads
> snd_una after taking it. Concurrent transmission and ACK processing can
> therefore leave the sampled upper bound behind snd_una. Active-open
> completion also exposes a reversed interval when it initializes snd_una
> to IDSN + 1 while the socket-owned state synchronization is deferred.
>
> [...]
Here is the summary with links:
- [net] mptcp: reject DATA_ACKs against a reversed send interval
https://git.kernel.org/netdev/net/c/d75e5cd72995
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:[~2026-11-10 19:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 13:07 [PATCH net] mptcp: reject DATA_ACKs against a reversed send interval Eric Dumazet
2026-11-04 13:13 ` netdev-bot+sinfo
2026-11-10 19:10 ` Matthieu Baerts
2026-11-10 19:33 ` Jakub Kicinski
2026-11-10 19:55 ` Matthieu Baerts
2026-11-10 19:50 ` 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=179434020493.26472.7236408102827538052.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=geliang@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=kylebot@openai.com \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.