On Fri, 2014-09-12 at 08:58 +0200, Henning Rogge wrote: [...] In general, this looks fine. However, > @@ -691,6 +719,9 @@ int mpp_path_add(struct ieee80211_sub_if_data *sdata, > > spin_unlock(&tbl->hashwlock[hash_idx]); > read_unlock_bh(&pathtbl_resize_lock); > + > + mpp_paths_generation++; This doesn't seem to be concurrency safe? Neither is the existing mesh_paths_generation++, I think, so maybe it's not something we really need to worry about? johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
