1. 16 9月, 2014 2 次提交
  2. 26 8月, 2014 1 次提交
  3. 26 6月, 2014 1 次提交
  4. 30 5月, 2014 1 次提交
    • A
      mwifiex: fix a crash in extended scan event processing · 21445049
      Avinash Patil 提交于
      [113.967694] Unable to handle kernel NULL pointer dereference
                     at virtual address 00000020
      ............
      [113.967859] PC is at mwifiex_update_rxreor_flags+0xfc/0x430
      ............
      [113.968110] mwifiex_update_rxreor_flags+0xfc/0x430
      [113.968129] mwifiex_handle_event_ext_scan_report+0x1e4/0x21c
      [113.968148] mwifiex_process_sta_event+0x410/0x508
      [113.968165] mwifiex_process_event+0x184/0x1e0
      [113.968181] mwifiex_main_process+0x220/0x48c
      [113.968197] mwifiex_sdio_interrupt+0xc8/0x1cc
      [113.968210] sdio_irq_thread+0x11c/0x290
      
      In case of legacy scan, adapter->curr_cmd is guranteed to be
      non-NULL in check_next_scan_cmd. This may not be case in
      extended scan where scan command response would come earlier and
      set curr_cmd to NULL. Extended scan event comes later and while
      trying to complete IOCTL for scan, driver would crash in
      dereferencing adapter->curr_cmd->wait_q_enabled.
      
      Avoid this by completing IOCTL in case of legacy scans only.
      Internal scan would be completed while handling extended scan
      command response.
      Signed-off-by: NAvinash Patil <patila@marvell.com>
      Signed-off-by: NBing Zhao <bzhao@marvell.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      21445049
  5. 23 4月, 2014 2 次提交
  6. 01 4月, 2014 1 次提交
  7. 28 3月, 2014 1 次提交
  8. 07 3月, 2014 1 次提交
  9. 01 3月, 2014 1 次提交
  10. 13 2月, 2014 5 次提交
  11. 14 1月, 2014 1 次提交
  12. 26 11月, 2013 1 次提交
    • L
      cfg80211: consolidate passive-scan and no-ibss flags · 8fe02e16
      Luis R. Rodriguez 提交于
      These two flags are used for the same purpose, just
      combine them into a no-ir flag to annotate no initiating
      radiation is allowed.
      
      Old userspace sending either flag will have it treated as
      the no-ir flag. To be considerate to older userspace we
      also send both the no-ir flag and the old no-ibss flags.
      Newer userspace will have to be aware of older kernels.
      
      Update all places in the tree using these flags with the
      following semantic patch:
      
      @@
      @@
      -NL80211_RRF_PASSIVE_SCAN
      +NL80211_RRF_NO_IR
      @@
      @@
      -NL80211_RRF_NO_IBSS
      +NL80211_RRF_NO_IR
      @@
      @@
      -IEEE80211_CHAN_PASSIVE_SCAN
      +IEEE80211_CHAN_NO_IR
      @@
      @@
      -IEEE80211_CHAN_NO_IBSS
      +IEEE80211_CHAN_NO_IR
      @@
      @@
      -NL80211_RRF_NO_IR | NL80211_RRF_NO_IR
      +NL80211_RRF_NO_IR
      @@
      @@
      -IEEE80211_CHAN_NO_IR | IEEE80211_CHAN_NO_IR
      +IEEE80211_CHAN_NO_IR
      @@
      @@
      -(NL80211_RRF_NO_IR)
      +NL80211_RRF_NO_IR
      @@
      @@
      -(IEEE80211_CHAN_NO_IR)
      +IEEE80211_CHAN_NO_IR
      
      Along with some hand-optimisations in documentation, to
      remove duplicates and to fix some indentation.
      Signed-off-by: NLuis R. Rodriguez <mcgrof@do-not-panic.com>
      [do all the driver updates in one go]
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      8fe02e16
  13. 02 8月, 2013 1 次提交
  14. 20 6月, 2013 2 次提交
  15. 23 5月, 2013 2 次提交
  16. 23 4月, 2013 2 次提交
  17. 04 4月, 2013 1 次提交
  18. 19 3月, 2013 1 次提交
  19. 19 2月, 2013 2 次提交
  20. 12 2月, 2013 1 次提交
  21. 05 2月, 2013 1 次提交
  22. 31 1月, 2013 1 次提交
    • B
      mwifiex: fix incomplete scan in case of IE parsing error · 8a7d7cbf
      Bing Zhao 提交于
      A scan request is split into multiple scan commands queued in
      scan_pending_q. Each scan command will be sent to firmware and
      its response is handlded one after another.
      
      If any error is detected while parsing IE in command response
      buffer the remaining data will be ignored and error is returned.
      
      We should check if there is any more scan commands pending in
      the queue before returning error. This ensures that we will call
      cfg80211_scan_done if this is the last scan command, or send
      next scan command in scan_pending_q to firmware.
      
      Cc: "3.6+" <stable@vger.kernel.org>
      Signed-off-by: NBing Zhao <bzhao@marvell.com>
      Signed-off-by: NAmitkumar Karwar <akarwar@marvell.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      8a7d7cbf
  23. 30 10月, 2012 4 次提交
  24. 25 10月, 2012 1 次提交
  25. 18 10月, 2012 1 次提交
    • A
      wireless: drivers: make use of WLAN_EID_VENDOR_SPECIFIC · 04b2312a
      Arend van Spriel 提交于
      The include file linux/ieee80211.h contains three definitions for
      the same thing in enum ieee80211_eid due to historic changes:
      
      /* Information Element IDs */
      enum ieee80211_eid {
          :
          WLAN_EID_WPA = 221,
          WLAN_EID_GENERIC = 221,
          WLAN_EID_VENDOR_SPECIFIC = 221,
          :
      };
      
      The standard refers to this as "vendor specific" element so the
      other two definitions are better not used. This patch changes the
      wireless drivers to use one definition, ie. WLAN_EID_VENDOR_SPECIFIC.
      
      Cc: Jouni Malinen <j@w1.fi>
      Cc: Dan Williams <dcbw@redhat.com>
      Cc: Larry Finger <Larry.Finger@lwfinger.net>
      Acked-by: Kalle Valo <kvalo@qca.qualcomm.com> [ath6kl]
      Acked-by: Bing Zhao <bzhao@marvell.com> [mwifiex]
      Acked-by: Stanislav Yakovlev <stas.yakovlev@gmail.com> [ipw2x00]
      Signed-off-by: NArend van Spriel <arend@broadcom.com>
      [change libipw as well]
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      04b2312a
  26. 09 10月, 2012 2 次提交