From: "Nishikawa, Kenzoh" <Kenzoh.Nishikawa@jp.sony.com>
To: 'Johannes Berg' <johannes@sipsolutions.net>
Cc: "'linux-wireless@vger.kernel.org'"
<linux-wireless@vger.kernel.org>,
"'devel@lists.open80211s.org'" <devel@lists.open80211s.org>,
"'Bob Copeland (me@bobcopeland.com)'" <me@bobcopeland.com>,
"'Thomas Pedersen (thomas@noack.us)'" <thomas@noack.us>
Subject: [Resend PATCH v5] mac80211: keep sending peer candidate events while in listen state
Date: Wed, 17 Dec 2014 11:01:11 +0000 [thread overview]
Message-ID: <2EB4F5C65A3B8E4E92660930F4EF6B5B07C4AC@JPYOKXMS113.jp.sony.com> (raw)
Instead of sending peer candidate events just once, send them
as long as the peer remains in the LISTEN state in the peering
state machine, when userspace is implementing the peering manager.
Userspace may silence the events from a peer by progressing
the state machine or by setting the link state to BLOCKED.
Fixes the problem that a mesh peering process won't be fired
again after the previous first peering trial fails due to like
air propagation error if the peering is managed by user space
such as wpa_supplicant.
This patch works with another patch for wpa_supplicant described
here which fires a peering process again triggered by the notice
from kernel.
http://lists.shmoo.com/pipermail/hostap/2014-November/031235.html
Signed-off-by: Kenzoh Nishikawa <Kenzoh.Nishikawa at jp.sony.com>
---
net/mac80211/mesh_plink.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/net/mac80211/mesh_plink.c b/net/mac80211/mesh_plink.c index 32c7bd0..dfc429b 100644
--- a/net/mac80211/mesh_plink.c
+++ b/net/mac80211/mesh_plink.c
@@ -524,6 +524,13 @@ void mesh_neighbour_update(struct ieee80211_sub_if_data *sdata,
sdata->u.mesh.mshcfg.auto_open_plinks &&
rssi_threshold_check(sta, sdata))
changed = mesh_plink_open(sta);
+ else if (sta->plink_state == NL80211_PLINK_LISTEN &&
+ (sdata->u.mesh.user_mpm ||
+ sdata->u.mesh.security & IEEE80211_MESH_SEC_AUTHED))
+ cfg80211_notify_new_peer_candidate(sdata->dev, hw_addr,
+ elems->ie_start,
+ elems->total_len,
+ GFP_ATOMIC);
ieee80211_mps_frame_release(sta, elems);
out:
reply other threads:[~2014-12-17 11:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2EB4F5C65A3B8E4E92660930F4EF6B5B07C4AC@JPYOKXMS113.jp.sony.com \
--to=kenzoh.nishikawa@jp.sony.com \
--cc=devel@lists.open80211s.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.com \
--cc=thomas@noack.us \
/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;
as well as URLs for NNTP newsgroup(s).