Linux kernel stable tree https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/atom?h=linux-2.6.39.y 2011-06-23T22:05:34+00:00 2011-06-23T22:05:34+00:00 Luciano Coelho coelho@ti.com 2011-05-18T21:43:38+00:00 urn:sha1:8220b32e2fd53d8b6afb103237a99634139769eb commit 208c72f4fe44fe09577e7975ba0e7fa0278f3d03 upstream. In both trigger_scan and sched_scan operations, we were checking for the SSID length before assigning the value correctly. Since the memory was just kzalloc'ed, the check was always failing and SSID with over 32 characters were allowed to go through. This was causing a buffer overflow when copying the actual SSID to the proper place. This bug has been there since 2.6.29-rc4. Signed-off-by: Luciano Coelho <coelho@ti.com> Signed-off-by: John W. Linville <linville@tuxdriver.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de> 2011-06-03T00:31:46+00:00 Jouni Malinen jouni.malinen@atheros.com 2011-05-04T05:45:16+00:00 urn:sha1:195a03999469b672c2a2a709b848db378bc57f2e commit 0e579d6a8f4aea346da818f13ee71401c125e639 upstream. Commit dbd2fd656f2060abfd3a16257f8b51ec60f6d2ed added a mechanism for user space to indicate whether a default key is being configured for only unicast or only multicast frames instead of all frames. This commit added a driver capability flag for indicating whether separate default keys are supported and validation of the set_key command based on that capability. However, this single capability flag is not enough to cover possible difference based on mode (AP/IBSS/STA) and the way this change was introduced resulted in a regression with drivers that do not indicate the new capability (i.e.., more or less any non-mac80211 driver using cfg80211) when using a recent wpa_supplicant snapshot. Fix the regression by removing the new check which is not strictly speaking needed. The new separate default key functionality is needed only for RSN IBSS which has a separate capability indication. Signed-off-by: Jouni Malinen <jouni.malinen@atheros.com> Signed-off-by: John W. Linville <linville@tuxdriver.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de> 2011-04-07T18:14:49+00:00 Linus Torvalds torvalds@linux-foundation.org 2011-04-07T18:14:49+00:00 urn:sha1:42933bac11e811f02200c944d8562a15f8ec4ff0 * 'for-linus2' of git://git.profusion.mobi/users/lucas/linux-2.6: Fix common misspellings 2011-03-31T14:26:23+00:00 Lucas De Marchi lucas.demarchi@profusion.mobi 2011-03-31T01:57:33+00:00 urn:sha1:25985edcedea6396277003854657b5f3cb31a628 Fixes generated by 'codespell' and manually reviewed. Signed-off-by: Lucas De Marchi <lucas.demarchi@profusion.mobi> 2011-03-28T19:42:02+00:00 Juuso Oikarinen juuso.oikarinen@nokia.com 2011-03-28T11:32:32+00:00 urn:sha1:2b78ac9bfc7483ba4bda9ad3d10dd4afcf88337c This patch adds to the fix "fix BSS double-unlinking" (commit 3207390a8b58bfc1335750f91cf6783c48ca19ca) by Johannes Berg. It turns out, that the double-unlinking scenario can also occur if expired BSS elements are removed whilst an interface is performing association. To work around that, replace list_del with list_del_init also in the "cfg80211_bss_expire" function, so that the check for whether the BSS still is in the list works correctly in cfg80211_unlink_bss. Signed-off-by: Juuso Oikarinen <juuso.oikarinen@nokia.com> Reviewed-by: Johannes Berg <johannes@sipsolutions.net> Signed-off-by: John W. Linville <linville@tuxdriver.com> 2011-03-28T19:42:02+00:00 Mariusz Kozlowski mk@lab.zgora.pl 2011-03-26T18:26:55+00:00 urn:sha1:bef9bacc4ec7ea6a02876164cd6ccaa4759edce4 In cfg80211_inform_bss_frame() wiphy is first dereferenced on privsz initialisation and then it is checked for NULL. This patch fixes that. Signed-off-by: Mariusz Kozlowski <mk@lab.zgora.pl> Acked-by: Johannes Berg <johannes@sipsolutions.net> Signed-off-by: John W. Linville <linville@tuxdriver.com> 2011-03-15T18:16:48+00:00 John W. Linville linville@tuxdriver.com 2011-03-15T18:16:48+00:00 urn:sha1:106af2c99a5249b809aaed45b8353ac087821f4a 2011-03-11T19:16:58+00:00 John W. Linville linville@tuxdriver.com 2011-03-07T21:17:59+00:00 urn:sha1:3677713b799155c96637cdef3fa025e42f3fcf48 Signed-off-by: John W. Linville <linville@tuxdriver.com> 2011-03-11T19:11:11+00:00 John W. Linville linville@tuxdriver.com 2011-03-11T19:11:11+00:00 urn:sha1:409ec36c320d580a036045e603f96286c362c609 2011-03-09T21:10:57+00:00 Scott James Remnant keybuk@google.com 2011-03-08T18:45:30+00:00 urn:sha1:4d9d88d121fdd01dd859717909ea3c90173f143a Regulatory devices issue change uevents to inform userspace of a need to call the crda tool; however these can often be sent before udevd is running, and were not previously included in the results of udevadm trigger (which requests a new change event using the /uevent attribute of the sysfs object). Add a uevent function to the device type which includes the COUNTRY information from the last request if it has yet to be processed, the case of multiple requests is already handled in the code by checking whether an unprocessed one is queued in the same manner and refusing to queue a new one. The existing udev rule continues to work as before. Signed-off-by: Scott James Remnant <keybuk@google.com> Acked-By: Kay Sievers <kay.sievers@vrfy.org> Acked-by: Greg Kroah-Hartman <gregkh@suse.de> Signed-off-by: John W. Linville <linville@tuxdriver.com>