summaryrefslogtreecommitdiffstats
path: root/kernel/rtmutex-debug.c
diff options
context:
space:
mode:
authorJohn W. Linville <linville@tuxdriver.com>2007-10-12 16:40:37 -0400
committerJohn W. Linville <linville@tuxdriver.com>2007-10-18 14:36:18 -0400
commit67a4cce4a89718d252b61aaf58882c69c0e2f6e3 (patch)
treec42df7a57412d20b62f6f1bbf9e509958c2d9079 /kernel/rtmutex-debug.c
parent52f095ee88d8851866bc7694ab991ca5abf21d5e (diff)
downloadop-kernel-dev-67a4cce4a89718d252b61aaf58882c69c0e2f6e3.zip
op-kernel-dev-67a4cce4a89718d252b61aaf58882c69c0e2f6e3.tar.gz
[PATCH] mac80211: make ieee802_11_parse_elems return void
Some APs send management frames with junk padding after the last IE. We already account for a similar problem with some Apple Airport devices, but at least one device is known to send more than a single extra byte. The device in question is the Draytek Vigor2900: http://www.draytek.com.au/products/Vigor2900.php The junk in question looks like an IE that runs off the end of the frame. This cause us to return ParseFailed. Since the frame in question is an association response, this causes us to fail to associate with this AP. The return code from ieee802_11_parse_elems is superfluous. All callers still check for the presence of the specific IEs that interest them anyway. So, remove the return code so the parse never "fails". Acked-by: Michael Wu <flamingice@sourmilk.net> Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'kernel/rtmutex-debug.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud