1. 08 12月, 2009 1 次提交
  2. 19 11月, 2009 1 次提交
  3. 11 11月, 2009 1 次提交
  4. 07 11月, 2009 1 次提交
  5. 05 11月, 2009 1 次提交
    • L
      rtl8187: Fix kernel oops when device is removed when LEDS enabled · 37b12dd2
      Larry Finger 提交于
      As reported by Rick Farina (sidhayn@gmail.com), removing the RTL8187
      USB stick, or unloading the driver rtl8187 using rmmod will cause a
      kernel oops.  There are at least two forms of the failure, (1) BUG:
      Scheduling while atomic, and (2) a fatal kernel page fault. This
      problem is reported in Bugzilla #14539.
      
      This problem does not occur for kernel 2.6.31, but does for 2.6.32-rc2,
      thus it is technically a regression; however, bisection did not locate
      any faulty patch. The fix was found by comparing the faulty code in
      rtl8187 with p54usb.  My interpretation is that the handling of work
      queues in mac80211 changed enough to the LEDs to be unregistered
      before tasks on the work queues are cancelled. Previously, these
      actions could be done in either order.
      
      (Herton Ronaldo Krzesinski <herton@mandriva.com.br> reports that the
      code is the same in 2.6.31, so this may be a candidate for 2.6.31.x.
      -- JWL)
      Signed-off-by: NLarry Finger <Larry.Finger@lwfinger.net>
      Reported-by: NRick Farina <sidhayn@gmail.com>
      Tested-by: NRick Farina <sidhayn@gmail.com>
      Cc: stable@kernel.org
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      37b12dd2
  6. 29 8月, 2009 2 次提交
    • H
      rtl8187: Implement rfkill support · ca9152e3
      Herton Ronaldo Krzesinski 提交于
      This change implements rfkill support for RTL8187B and RTL8187L devices,
      using new cfg80211 rfkill API.
      Acked-by: NLarry Finger <Larry.Finger@lwfinger.net>
      Tested-by: NHin-Tak Leung <htl10@users.sourceforge.net>
      Signed-off-by: NHerton Ronaldo Krzesinski <herton@mandriva.com.br>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      ca9152e3
    • H
      rtl8187: fix circular locking (rtl8187_stop/rtl8187_work) · 6a8171f2
      Herton Ronaldo Krzesinski 提交于
      Larry Finger reports following lockdep warning:
      
      [ INFO: possible circular locking dependency detected ]
      2.6.31-rc6-wl #201
      -------------------------------------------------------
      rfkill/30578 is trying to acquire lock:
       (&(&priv->work)->work#2){+.+...}, at: [<ffffffff81051215>]
      __cancel_work_timer+0xd9/0x222
      
      but task is already holding lock:
       (&priv->conf_mutex#2){+.+.+.}, at: [<ffffffffa064a024>]
      rtl8187_stop+0x31/0x364 [rtl8187]
      
      which lock already depends on the new lock.
      
      the existing dependency chain (in reverse order) is:
      
      -> #1 (&priv->conf_mutex#2){+.+.+.}:
             [<ffffffff81065957>] __lock_acquire+0x12d0/0x1614
             [<ffffffff81065d54>] lock_acquire+0xb9/0xdd
             [<ffffffff8127c32f>] mutex_lock_nested+0x56/0x2a8
             [<ffffffffa064a392>] rtl8187_work+0x3b/0xf2 [rtl8187]
             [<ffffffff81050758>] worker_thread+0x1fa/0x30a
             [<ffffffff81054ca5>] kthread+0x8f/0x97
             [<ffffffff8100cb7a>] child_rip+0xa/0x20
             [<ffffffffffffffff>] 0xffffffffffffffff
      
      -> #0 (&(&priv->work)->work#2){+.+...}:
             [<ffffffff8106568c>] __lock_acquire+0x1005/0x1614
             [<ffffffff81065d54>] lock_acquire+0xb9/0xdd
             [<ffffffff8105124e>] __cancel_work_timer+0x112/0x222
             [<ffffffff8105136b>] cancel_delayed_work_sync+0xd/0xf
             [<ffffffffa064a33f>] rtl8187_stop+0x34c/0x364 [rtl8187]
             [<ffffffffa0242866>] ieee80211_stop_device+0x29/0x61 [mac80211]
             [<ffffffffa0239194>] ieee80211_stop+0x476/0x530 [mac80211]
             [<ffffffff8120ce15>] dev_close+0x8a/0xac
             [<ffffffffa01d9fa7>] cfg80211_rfkill_set_block+0x4a/0x7a [cfg80211]
             [<ffffffffa01bf4f0>] rfkill_set_block+0x84/0xd9 [rfkill]
             [<ffffffffa01bfc31>] rfkill_fop_write+0xda/0x124 [rfkill]
             [<ffffffff810cf286>] vfs_write+0xae/0x14a
             [<ffffffff810cf3e6>] sys_write+0x47/0x6e
             [<ffffffff8100ba6b>] system_call_fastpath+0x16/0x1b
             [<ffffffffffffffff>] 0xffffffffffffffff
      
      The problem here is that rtl8187_stop, while helding priv->conf_mutex,
      runs cancel_delayed_work_sync on an workqueue that runs rtl8187_work,
      which also takes priv->conf_mutex lock. Move cancel_delayed_work_sync
      out of rtl8187_stop priv->conf_mutex locking region.
      Reported-by: NLarry Finger <Larry.Finger@lwfinger.net>
      Tested-by: NLarry Finger <Larry.Finger@lwfinger.net>
      Signed-off-by: NHerton Ronaldo Krzesinski <herton@mandriva.com.br>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      6a8171f2
  7. 22 8月, 2009 1 次提交
  8. 20 8月, 2009 1 次提交
    • J
      mac80211: allow configure_filter callback to sleep · 3ac64bee
      Johannes Berg 提交于
      Over time, a whole bunch of drivers have come up
      with their own scheme to delay the configure_filter
      operation to a workqueue. To be able to simplify
      things, allow configure_filter to sleep, and add
      a new prepare_multicast callback that drivers that
      need the multicast address list implement. This new
      callback must be atomic, but most drivers either
      don't care or just calculate a hash which can be
      done atomically and then uploaded to the hardware
      non-atomically.
      
      A cursory look suggests that at76c50x-usb, ar9170,
      mwl8k (which is actually very broken now), rt2x00,
      wl1251, wl1271 and zd1211 should make use of this
      new capability.
      Signed-off-by: NJohannes Berg <johannes@sipsolutions.net>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      3ac64bee
  9. 14 8月, 2009 1 次提交
  10. 05 8月, 2009 1 次提交
    • L
      mac80211: redefine usage of the mac80211 workqueue · 42935eca
      Luis R. Rodriguez 提交于
      The mac80211 workqueue exists to enable mac80211 and drivers
      to queue their own work on a single threaded workqueue. mac80211
      takes care to flush the workqueue during suspend but we never
      really had requirements on drivers for how they should use
      the workqueue in consideration for suspend.
      
      We extend mac80211 to document how the mac80211 workqueue should
      be used, how it should not be used and finally move raw access to
      the workqueue to mac80211 only. Drivers and mac80211 use helpers
      to queue work onto the mac80211 workqueue:
      
        * ieee80211_queue_work()
        * ieee80211_queue_delayed_work()
      
      These helpers will now warn if mac80211 already completed its
      suspend cycle and someone is trying to queue work. mac80211
      flushes the mac80211 workqueue prior to suspend a few times,
      but we haven't taken the care to ensure drivers won't add more
      work after suspend. To help with this we add a warning when
      someone tries to add work and mac80211 already completed the
      suspend cycle.
      
      Drivers should ensure they cancel any work or delayed work
      in the mac80211 stop() callback.
      Signed-off-by: NLuis R. Rodriguez <lrodriguez@atheros.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      42935eca
  11. 22 7月, 2009 1 次提交
  12. 11 7月, 2009 2 次提交
  13. 29 5月, 2009 1 次提交
  14. 28 5月, 2009 1 次提交
  15. 12 5月, 2009 1 次提交
  16. 07 5月, 2009 1 次提交
  17. 23 4月, 2009 2 次提交
  18. 24 2月, 2009 1 次提交
  19. 30 1月, 2009 4 次提交
  20. 24 1月, 2009 1 次提交
  21. 13 1月, 2009 2 次提交
  22. 20 12月, 2008 2 次提交
  23. 13 12月, 2008 2 次提交
  24. 05 12月, 2008 1 次提交
  25. 26 11月, 2008 5 次提交
  26. 22 11月, 2008 2 次提交