mac80211: don't clear next_hop in path reclaim
authorJohannes Berg <johannes@sipsolutions.net>
Tue, 26 Feb 2008 09:53:57 +0000 (10:53 +0100)
committerJohn W. Linville <linville@tuxdriver.com>
Thu, 6 Mar 2008 20:30:47 +0000 (15:30 -0500)
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>
net/mac80211/mesh_pathtbl.c

index a17f2b299045811fbd35f9ad67b5ddbbd08f958a..ab4d757c453b7e39aa3fc449b3b040419fde0e00 100644 (file)
@@ -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);