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: [net v2 0/2] Fix rcu_read_lock issues in netdev-genl
Date: Wed, 13 Nov 2024 02:17:50 +0000 [thread overview]
Message-ID: <20241113021755.11125-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 proposes 2 patches:
- Patch 1:
- Fixes a similar issue in an older commit and CCs stable as this
fix could be backported.
- Patch 2:
- Fixes the issue Paolo hit while running the selftest
I retested locally after applying this series and confirmed that the
splat is fixed.
Thanks,
Joe
[1]: https://lore.kernel.org/netdev/719083c2-e277-447b-b6ea-ca3acb293a03@redhat.com/
v2:
- Removed the helper and simplified to just add a rcu_read_lock /
unlock in both patches instead.
rfc: https://lore.kernel.org/lkml/20241112181401.9689-1-jdamato@fastly.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 | 4 ++++
1 file changed, 4 insertions(+)
base-commit: a58f00ed24b849d449f7134fd5d86f07090fe2f5
--
2.25.1
next reply other threads:[~2024-11-13 2:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 2:17 Joe Damato [this message]
2024-11-13 2:17 ` [net v2 1/2] netdev-genl: Hold rcu_read_lock in napi_get Joe Damato
2024-11-13 2:17 ` [net v2 2/2] netdev-genl: Hold rcu_read_lock in napi_set Joe Damato
2024-11-14 2:47 ` [net v2 0/2] Fix rcu_read_lock issues in netdev-genl Jakub Kicinski
2024-11-14 6:29 ` Joe Damato
2024-11-14 9:06 ` Paolo Abeni
2024-11-14 17:58 ` Joe Damato
2024-11-14 18:32 ` Paolo Abeni
2024-11-14 19:31 ` Jakub Kicinski
2024-11-14 20:13 ` 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=20241113021755.11125-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®