summaryrefslogtreecommitdiff
path: root/kernel/sysctl.c
diff options
context:
space:
mode:
authorJohannes Berg <johannes.berg@intel.com>2013-04-10 19:38:36 (GMT)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2013-04-25 19:51:22 (GMT)
commit7ac7dd50d62c02b055f4e7f53b39040f863ff48a (patch)
tree03eea3c334384c655d06117ef2c1014f10a46cb1 /kernel/sysctl.c
parent42a2d01229b66c76d96fc2e5eb96e8d9c3caaac0 (diff)
downloadlinux-fsl-qoriq-7ac7dd50d62c02b055f4e7f53b39040f863ff48a.tar.xz
mac80211: fix cfg80211 interaction on auth/assoc request
commit 7b119dc06d871405fc7c3e9a73a6c987409ba639 upstream. If authentication (or association with FT) is requested by userspace, mac80211 currently doesn't tell cfg80211 that it disconnected from the AP. That leaves inconsistent state: cfg80211 thinks it's connected while mac80211 thinks it's not. Typically this won't last long, as soon as mac80211 reports the new association to cfg80211 the old one goes away. If, however, the new authentication or association doesn't succeed, then cfg80211 will forever think the old one still exists and will refuse attempts to authenticate or associate with the AP it thinks it's connected to. Anders reported that this leads to it taking a very long time to reconnect to a network, or never even succeeding. I tested this with an AP hacked to never respond to auth frames, and one that works, and with just those two the system never recovers because one won't work and cfg80211 thinks it's connected to the other so refuses connections to it. To fix this, simply make mac80211 tell cfg80211 when it is no longer connected to the old AP, while authenticating or associating to a new one. Reported-by: Anders Kaseorg <andersk@mit.edu> Signed-off-by: Johannes Berg <johannes.berg@intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'kernel/sysctl.c')
0 files changed, 0 insertions, 0 deletions