Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1432892 > unrolled thread

[PATCH] mac80211: util: mesh is not connected properly after recovery

Started byYaniv Machani <yanivma@ti.com>
First post2016-06-28 13:40 +0200
Last post2016-06-29 09:30 +0200
Articles 3 — 2 participants

Back to article view | Back to linux.kernel


Contents

  [PATCH] mac80211: util: mesh is not connected properly after recovery Yaniv Machani <yanivma@ti.com> - 2016-06-28 13:40 +0200
    Re: [PATCH] mac80211: util: mesh is not connected properly after  recovery Johannes Berg <johannes@sipsolutions.net> - 2016-06-29 09:30 +0200
    Re: [PATCH] mac80211: util: mesh is not connected properly after  recovery Johannes Berg <johannes@sipsolutions.net> - 2016-06-29 09:30 +0200

#1432892 — [PATCH] mac80211: util: mesh is not connected properly after recovery

FromYaniv Machani <yanivma@ti.com>
Date2016-06-28 13:40 +0200
Subject[PATCH] mac80211: util: mesh is not connected properly after recovery
Message-ID<rOZwZ-6qc-13@gated-at.bofh.it>
From: Maital Hahn <maitalm@ti.com>

In the reconfigure process for mesh interface, moved the reconfiguration
of the mesh peers to be done only after restarting the beacons,
the same as it is done for AP.

Signed-off-by: Maital Hahn <maitalm@ti.com>
Acked-by: Yaniv Machani <yanivma@ti.com>
---
 net/mac80211/util.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/net/mac80211/util.c b/net/mac80211/util.c
index 5375a82..2431684 100644
--- a/net/mac80211/util.c
+++ b/net/mac80211/util.c
@@ -1910,6 +1910,7 @@ int ieee80211_reconfig(struct ieee80211_local *local)
 			ieee80211_reconfig_stations(sdata);
 			/* fall through */
 		case NL80211_IFTYPE_AP: /* AP stations are handled later */
+		case NL80211_IFTYPE_MESH_POINT: /* MP peers are handled later */
 			for (i = 0; i < IEEE80211_NUM_ACS; i++)
 				drv_conf_tx(local, sdata, i,
 					    &sdata->tx_conf[i]);
@@ -2013,7 +2014,8 @@ int ieee80211_reconfig(struct ieee80211_local *local)
 		if (!sta->uploaded)
 			continue;
 
-		if (sta->sdata->vif.type != NL80211_IFTYPE_AP)
+		if ((sta->sdata->vif.type != NL80211_IFTYPE_AP) &&
+		    (sta->sdata->vif.type != NL80211_IFTYPE_MESH_POINT))
 			continue;
 
 		for (state = IEEE80211_STA_NOTEXIST;
-- 
2.9.0

[toc] | [next] | [standalone]


#1433512 — Re: [PATCH] mac80211: util: mesh is not connected properly after recovery

FromJohannes Berg <johannes@sipsolutions.net>
Date2016-06-29 09:30 +0200
SubjectRe: [PATCH] mac80211: util: mesh is not connected properly after recovery
Message-ID<rPi6B-1fN-7@gated-at.bofh.it>
In reply to#1432892
On Tue, 2016-06-28 at 14:15 +0300, Yaniv Machani wrote:
> From: Maital Hahn <maitalm@ti.com>
> 
> In the reconfigure process for mesh interface, moved the
> reconfiguration
> of the mesh peers to be done only after restarting the beacons,
> the same as it is done for AP.
> 
> Signed-off-by: Maital Hahn <maitalm@ti.com>
> Acked-by: Yaniv Machani <yanivma@ti.com>
> 
Same here, and this also needs a description of why this is OK with
other drivers, since presumably it already works there.

johannes

[toc] | [prev] | [next] | [standalone]


#1433514 — Re: [PATCH] mac80211: util: mesh is not connected properly after recovery

FromJohannes Berg <johannes@sipsolutions.net>
Date2016-06-29 09:30 +0200
SubjectRe: [PATCH] mac80211: util: mesh is not connected properly after recovery
Message-ID<rPi6C-1fN-17@gated-at.bofh.it>
In reply to#1432892
Also - your subject lines should explain the *fix*, not the *bug*

johannes

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web