From: patchwork-bot+netdevbpf@kernel.org
To: Wang Hai <wanghai38@huawei.com>
Cc: kerneljasonxing@gmail.com, edumazet@google.com,
ncardwell@google.com, kuniyu@amazon.com, davem@davemloft.net,
dsahern@kernel.org, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, zhangchangzhong@huawei.com,
liujian56@huawei.com, yuehaibing@huawei.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 net] tcp: Defer ts_recent changes until req is owned
Date: Wed, 26 Feb 2025 09:00:29 +0000 [thread overview]
Message-ID: <174056042930.623394.10264696508717158233.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250224090047.50748-1-wanghai38@huawei.com>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Mon, 24 Feb 2025 17:00:47 +0800 you wrote:
> Recently a bug was discovered where the server had entered TCP_ESTABLISHED
> state, but the upper layers were not notified.
>
> The same 5-tuple packet may be processed by different CPUSs, so two
> CPUs may receive different ack packets at the same time when the
> state is TCP_NEW_SYN_RECV.
>
> [...]
Here is the summary with links:
- [v3,net] tcp: Defer ts_recent changes until req is owned
https://git.kernel.org/netdev/net/c/8d52da23b6c6
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-02-26 8:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 9:00 [PATCH v3 net] tcp: Defer ts_recent changes until req is owned Wang Hai
2025-02-24 9:22 ` Eric Dumazet
2025-02-25 21:16 ` Kuniyuki Iwashima
2025-02-26 9:00 ` 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=174056042930.623394.10264696508717158233.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kerneljasonxing@gmail.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liujian56@huawei.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wanghai38@huawei.com \
--cc=yuehaibing@huawei.com \
--cc=zhangchangzhong@huawei.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;
as well as URLs for NNTP newsgroup(s).