From: patchwork-bot+netdevbpf@kernel.org
To: luoxuanqiang <luoxuanqiang@kylinos.cn>
Cc: kuniyu@amazon.com, edumazet@google.com, kuba@kernel.org,
davem@davemloft.net, pabeni@redhat.com, dccp@vger.kernel.org,
dsahern@kernel.org, fw@strlen.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, alexandre.ferrieux@orange.com
Subject: Re: [PATCH net v4] Fix race for duplicate reqsk on identical SYN
Date: Tue, 25 Jun 2024 09:50:35 +0000 [thread overview]
Message-ID: <171930903510.26753.16745690029094137653.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240621013929.1386815-1-luoxuanqiang@kylinos.cn>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 21 Jun 2024 09:39:29 +0800 you wrote:
> When bonding is configured in BOND_MODE_BROADCAST mode, if two identical
> SYN packets are received at the same time and processed on different CPUs,
> it can potentially create the same sk (sock) but two different reqsk
> (request_sock) in tcp_conn_request().
>
> These two different reqsk will respond with two SYNACK packets, and since
> the generation of the seq (ISN) incorporates a timestamp, the final two
> SYNACK packets will have different seq values.
>
> [...]
Here is the summary with links:
- [net,v4] Fix race for duplicate reqsk on identical SYN
https://git.kernel.org/netdev/net/c/ff46e3b44219
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-06-25 9:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 1:39 [PATCH net v4] Fix race for duplicate reqsk on identical SYN luoxuanqiang
2024-06-21 22:48 ` Kuniyuki Iwashima
2024-06-24 13:56 ` Eric Dumazet
2024-06-25 9:49 ` Paolo Abeni
2024-06-26 7:12 ` luoxuanqiang
2024-06-25 9: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=171930903510.26753.16745690029094137653.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.ferrieux@orange.com \
--cc=davem@davemloft.net \
--cc=dccp@vger.kernel.org \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luoxuanqiang@kylinos.cn \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox