From: patchwork-bot+netdevbpf@kernel.org
To: Bobby Eshleman <bobbyeshleman@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, almasrymina@google.com,
kaiyuanz@google.com, sdf@fomichev.me, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, bobbyeshleman@meta.com
Subject: Re: [PATCH net v2] net: devmem: use READ_ONCE/WRITE_ONCE on binding->dev
Date: Thu, 05 Mar 2026 02:20:08 +0000 [thread overview]
Message-ID: <177267720804.2482446.3695748884408177955.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260302-devmem-membar-fix-v2-1-5b33c9cbc28b@meta.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 02 Mar 2026 16:32:56 -0800 you wrote:
> From: Bobby Eshleman <bobbyeshleman@meta.com>
>
> binding->dev is protected on the write-side in
> mp_dmabuf_devmem_uninstall() against concurrent writes, but due to the
> concurrent bare reads in net_devmem_get_binding() and
> validate_xmit_unreadable_skb() it should be wrapped in a
> READ_ONCE/WRITE_ONCE pair to make sure no compiler optimizations play
> with the underlying register in unforeseen ways.
>
> [...]
Here is the summary with links:
- [net,v2] net: devmem: use READ_ONCE/WRITE_ONCE on binding->dev
https://git.kernel.org/netdev/net/c/40bf00ec2ee2
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-03-05 2:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 0:32 [PATCH net v2] net: devmem: use READ_ONCE/WRITE_ONCE on binding->dev Bobby Eshleman
2026-03-05 2:20 ` 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=177267720804.2482446.3695748884408177955.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=almasrymina@google.com \
--cc=bobbyeshleman@gmail.com \
--cc=bobbyeshleman@meta.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kaiyuanz@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
/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