From: Mohsin Bashir <mohsin.bashr@gmail.com>
To: Simon Horman <horms@kernel.org>
Cc: netdev@vger.kernel.org, kuba@kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
shuah@kernel.org, cratiu@nvidia.com, noren@nvidia.com,
cjubran@nvidia.com, mbloch@nvidia.com, jdamato@fastly.com,
gal@nvidia.com, sdf@fomichev.me, ast@kernel.org,
daniel@iogearbox.net, hawk@kernel.org, john.fastabend@gmail.com,
nathan@kernel.org, nick.desaulniers+lkml@gmail.com,
morbo@google.com, justinstitt@google.com, bpf@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next V4 1/5] net: netdevsim: hook in XDP handling
Date: Tue, 15 Jul 2025 11:44:06 -0700 [thread overview]
Message-ID: <f0bce278-4162-4003-bd60-072f7360d452@gmail.com> (raw)
In-Reply-To: <20250715134740.GA1341824@horms.kernel.org>
>> + ns = netdev_priv(dev);
>> + xdp_prog = rcu_dereference(ns->xdp.prog);
>
> I'm somewhat confused by this because ns->xdp.prog doesn't appear to be
> protected by RCU.
>
> Flagged by Sparse.
Right. Thanks for pointing out Simon. I'll fix it.
next prev parent reply other threads:[~2025-07-15 18:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 21:03 [PATCH net-next V4 0/5] selftests: drv-net: Test XDP native support Mohsin Bashir
2025-07-14 21:03 ` [PATCH net-next V4 1/5] net: netdevsim: hook in XDP handling Mohsin Bashir
2025-07-15 13:47 ` Simon Horman
2025-07-15 18:44 ` Mohsin Bashir [this message]
2025-07-15 17:36 ` kernel test robot
2025-07-14 21:03 ` [PATCH net-next V4 2/5] selftests: drv-net: Test XDP_PASS/DROP support Mohsin Bashir
2025-07-14 21:03 ` [PATCH net-next V4 3/5] selftests: drv-net: Test XDP_TX support Mohsin Bashir
2025-07-14 21:03 ` [PATCH net-next V4 4/5] selftests: drv-net: Test tail-adjustment support Mohsin Bashir
2025-07-14 21:03 ` [PATCH net-next V4 5/5] selftests: drv-net: Test head-adjustment support Mohsin Bashir
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=f0bce278-4162-4003-bd60-072f7360d452@gmail.com \
--to=mohsin.bashr@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=cjubran@nvidia.com \
--cc=cratiu@nvidia.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=jdamato@fastly.com \
--cc=john.fastabend@gmail.com \
--cc=justinstitt@google.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=noren@nvidia.com \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
/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).