From: Joe Damato <jdamato@fastly.com>
To: netdev@vger.kernel.org
Cc: pabeni@redhat.com, edumazet@google.com,
amritha.nambiar@intel.com, sridhar.samudrala@intel.com,
kuba@kernel.org, mkarsten@uwaterloo.ca,
Joe Damato <jdamato@fastly.com>,
"David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org (open list),
Mina Almasry <almasrymina@google.com>,
Simon Horman <horms@kernel.org>
Subject: [RFC net 0/2] Fix rcu_read_lock issues in netdev-genl
Date: Tue, 12 Nov 2024 18:13:57 +0000 [thread overview]
Message-ID: <20241112181401.9689-1-jdamato@fastly.com> (raw)
Greetings:
Paolo reported a splat [1] when running the new selftest for busy poll.
I confirmed and reproduced this splat locally.
This series proposed 2 patches, which:
- Patch 1:
- Adds a helper function to reduce code duplication that sets the
error, extack, napi, etc.
- Fixes a similar issue in an older commit and CCs stable as this
fix could be backported.
- Patch 2:
- Uses the helper added in 1 to fix the recently added commit that
adds netdev_nl_napi_set_doit which is exercised by the selftest
triggering the splat that Paolo reported.
I retested locally after applying this series and confirmed that the
splat is fixed.
Note: I only CC'd stable on patch 1 because that code goes back a few
releases. patch 2 is fixing code merged very recently that does not yet
appear in any RC and so I've omit the CC for stable there. I've sent
this as an RFC because I am not sure if that's the right thing to do.
Let me know and I'll be happy to re-send (after 24hr) an official
series.
Thanks,
Joe
[1]: https://lore.kernel.org/netdev/719083c2-e277-447b-b6ea-ca3acb293a03@redhat.com/
Joe Damato (2):
netdev-genl: Hold rcu_read_lock in napi_get
netdev-genl: Hold rcu_read_lock in napi_set
net/core/netdev-genl.c | 37 +++++++++++++++++++++++++------------
1 file changed, 25 insertions(+), 12 deletions(-)
base-commit: a58f00ed24b849d449f7134fd5d86f07090fe2f5
--
2.25.1
next reply other threads:[~2024-11-12 18:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 18:13 Joe Damato [this message]
2024-11-12 18:13 ` [RFC net 1/2] netdev-genl: Hold rcu_read_lock in napi_get Joe Damato
2024-11-13 1:28 ` Jakub Kicinski
2024-11-13 1:48 ` Joe Damato
2024-11-13 2:01 ` Jakub Kicinski
2024-11-13 2:05 ` Joe Damato
2024-11-12 18:13 ` [RFC net 2/2] netdev-genl: Hold rcu_read_lock in napi_set Joe Damato
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=20241112181401.9689-1-jdamato@fastly.com \
--to=jdamato@fastly.com \
--cc=almasrymina@google.com \
--cc=amritha.nambiar@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkarsten@uwaterloo.ca \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sridhar.samudrala@intel.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
all inboxes | Powered by JetHome®