diff options
author | Johannes Berg <johannes.berg@intel.com> | 2014-02-21 19:34:34 (GMT) |
---|---|---|
committer | Jiri Slaby <jslaby@suse.cz> | 2014-03-22 21:01:49 (GMT) |
commit | 4032900fb38c1c7436f0b216a6687fc96c989f5d (patch) | |
tree | 1908337c21c069c543569c321b9bd009be555619 /samples/trace_events/Makefile | |
parent | 58d4310586466840dab77e56e53f4508853a5268 (diff) | |
download | linux-fsl-qoriq-4032900fb38c1c7436f0b216a6687fc96c989f5d.tar.xz |
mac80211: don't validate unchanged AP bandwidth while tracking
commit 963a1852fbac4f75a2d938fa2e734ef1e6d4c044 upstream.
The MLME code in mac80211 must track whether or not the AP changed
bandwidth, but if there's no change while tracking it shouldn't do
anything, otherwise regulatory updates can make it impossible to
connect to certain APs if the regulatory database doesn't match the
information from the AP. See the precise scenario described in the
code.
This still leaves some possible problems with CSA or if the AP
actually changed bandwidth, but those cases are less common and
won't completely prevent using it.
This fixes https://bugzilla.kernel.org/show_bug.cgi?id=70881
Reported-and-tested-by: Nate Carlson <kernel@natecarlson.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Jiri Slaby <jslaby@suse.cz>
Diffstat (limited to 'samples/trace_events/Makefile')
0 files changed, 0 insertions, 0 deletions