From: patchwork-bot+netdevbpf@kernel.org
To: Runyu Xiao <runyu.xiao@seu.edu.cn>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org, horms@kernel.org,
linux-kernel@vger.kernel.org, jianhao.xu@seu.edu.cn
Subject: Re: [PATCH net] kcm: use WRITE_ONCE() when changing lower socket callbacks
Date: Sun, 14 Jun 2026 08:30:11 +0000 [thread overview]
Message-ID: <178142581139.1725970.11900596432572188440.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260611053543.2429462-1-runyu.xiao@seu.edu.cn>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 11 Jun 2026 13:35:43 +0800 you wrote:
> kcm_attach() replaces a live lower TCP socket's sk_data_ready and
> sk_write_space callbacks with KCM handlers, and kcm_unattach() restores
> them later. Those callback-pointer updates are still plain stores even
> though the same fields can be read and invoked concurrently on other
> CPUs.
>
> If another CPU observes an older callback snapshot after the live field
> has already been restored, callback execution can run with a mismatched
> target and sk_user_data state, leading to stale or misdirected wakeups.
>
> [...]
Here is the summary with links:
- [net] kcm: use WRITE_ONCE() when changing lower socket callbacks
https://git.kernel.org/netdev/net/c/47186409c092
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-06-14 8:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 5:35 [PATCH net] kcm: use WRITE_ONCE() when changing lower socket callbacks Runyu Xiao
2026-06-14 8:30 ` 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=178142581139.1725970.11900596432572188440.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jianhao.xu@seu.edu.cn \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=runyu.xiao@seu.edu.cn \
/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