cfg80211: fix rfkill locking problem
authorJohannes Berg <johannes@sipsolutions.net>
Wed, 10 Jun 2009 14:50:29 +0000 (16:50 +0200)
committerJohn W. Linville <linville@tuxdriver.com>
Wed, 10 Jun 2009 17:28:41 +0000 (13:28 -0400)
commit2f0accc13520b2644b85f80aedce10d10d88b0ca
tree7c5ce603af5b3e3e738737f464684ce121cc7fdd
parent4e751843d406a4d0471c207872b9e24957de8357
cfg80211: fix rfkill locking problem

rfkill currently requires a global lock within the
rfkill_register() function, and holds that lock over
calls to the set_block() methods. This means that we
cannot hold a lock around rfkill_register() that we
also require in set_block(), directly or indirectly.
Fix cfg80211 to register rfkill outside the block
locked by its global lock. Much of what cfg80211 does
in the locked block doesn't need to be locked anyway.

Reported-by: Vasanthakumar Thiagarajan <vasanth@atheros.com>
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
net/wireless/core.c