From: Thomas Pedersen <thomas@eero.com>
To: linux-wireless@vger.kernel.org
Cc: Johannes Berg <johannes.berg@intel.com>,
peter.oh@bowerswilkins.com, Thomas Pedersen <thomas@eero.com>
Subject: [PATCH] mac80211: mesh: fix RCU warning
Date: Wed, 15 May 2019 15:21:46 -0700 [thread overview]
Message-ID: <1557958906-1432-1-git-send-email-thomas@eero.com> (raw)
ifmsh->csa was being dereferenced without the RCU read
lock held.
fixes the following warning:
[ 74.930435] =============================
[ 74.932066] WARNING: suspicious RCU usage
[ 74.933671] 4.20.13 #5 Tainted: G W
[ 74.935804] -----------------------------
[ 74.937427] net/mac80211/mesh.c:1218 suspicious rcu_dereference_check() usage!
[ 74.940473] other info that might help us debug this:
[ 74.943654] rcu_scheduler_active = 2, debug_locks = 1
[ 74.946311] 5 locks held by kworker/u8:3/107:
[ 74.948087] #0: 000000007623c1f0 ((wq_completion)"%s"wiphy_name(local->hw.wiphy)){+.+.}, at: process_one_work+0x1a2/0x610
[ 74.952464] #1: 00000000077b4215 ((work_completion)(&sdata->csa_finalize_work)){+.+.}, at: process_one_work+0x1a2/0x610
[ 74.957228] #2: 00000000e02b12da (&wdev->mtx){+.+.}, at: ieee80211_csa_finalize_work+0x2f/0x90
[ 74.959870] #3: 00000000e6855095 (&local->mtx){+.+.}, at: ieee80211_csa_finalize_work+0x47/0x90
[ 74.962937] #4: 00000000bb5e3bca (&local->chanctx_mtx){+.+.}, at: ieee80211_csa_finalize_work+0x51/0x90
Signed-off-by: Thomas Pedersen <thomas@eero.com>
---
net/mac80211/mesh.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/net/mac80211/mesh.c b/net/mac80211/mesh.c
index 766e5e5..70aeb34 100644
--- a/net/mac80211/mesh.c
+++ b/net/mac80211/mesh.c
@@ -1220,10 +1220,12 @@ int ieee80211_mesh_finish_csa(struct ieee80211_sub_if_data *sdata)
ifmsh->chsw_ttl = 0;
/* Remove the CSA and MCSP elements from the beacon */
+ rcu_read_lock();
tmp_csa_settings = rcu_dereference(ifmsh->csa);
RCU_INIT_POINTER(ifmsh->csa, NULL);
if (tmp_csa_settings)
kfree_rcu(tmp_csa_settings, rcu_head);
+ rcu_read_unlock();
ret = ieee80211_mesh_rebuild_beacon(sdata);
if (ret)
return -EINVAL;
--
2.7.4
next reply other threads:[~2019-05-15 22:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 22:21 Thomas Pedersen [this message]
2019-05-15 22:24 ` [PATCH] mac80211: mesh: fix RCU warning Thomas Pedersen
2019-05-24 8:29 ` Johannes Berg
2019-05-25 3:46 ` Thomas Pedersen
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=1557958906-1432-1-git-send-email-thomas@eero.com \
--to=thomas@eero.com \
--cc=johannes.berg@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=peter.oh@bowerswilkins.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