From: Johannes Berg <johannes@sipsolutions.net>
Date: Tue, 26 Feb 2008 09:53:57 +0000 (+0100)
Subject: mac80211: don't clear next_hop in path reclaim
X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=7c8076bd8be3fd2a9a94f9687cf39e3505f0e4ec;p=GitHub%2FLineageOS%2Fandroid_kernel_motorola_exynos9610.git

mac80211: don't clear next_hop in path reclaim

Luis pointed out that this path is going to be freed right
away anyway so there's no point in assigning next_hop.

Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Cc: Luis Carlos Cobo <luisca@cozybit.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
---

diff --git a/net/mac80211/mesh_pathtbl.c b/net/mac80211/mesh_pathtbl.c
index a17f2b299045..ab4d757c453b 100644
--- a/net/mac80211/mesh_pathtbl.c
+++ b/net/mac80211/mesh_pathtbl.c
@@ -301,7 +301,6 @@ static void mesh_path_node_reclaim(struct rcu_head *rp)
 	struct ieee80211_sub_if_data *sdata =
 		IEEE80211_DEV_TO_SUB_IF(node->mpath->dev);
 
-	rcu_assign_pointer(node->mpath->next_hop, NULL);
 	atomic_dec(&sdata->u.sta.mpaths);
 	kfree(node->mpath);
 	kfree(node);