regulatory: clarify locking rules and assertions
authorJohannes Berg <johannes.berg@intel.com>
Mon, 3 Dec 2012 22:00:08 +0000 (23:00 +0100)
committerJohannes Berg <johannes.berg@intel.com>
Thu, 3 Jan 2013 12:01:27 +0000 (13:01 +0100)
commite8da2bb4fe9ecb888f44714e2624c7d4268ac09d
treec776f0786e9d72c34888a25cec998f348ef64d70
parent5d885b999c68283c493cf00cc020260d38951ae6
regulatory: clarify locking rules and assertions

Many places that currently check that cfg80211_mutex
is held don't actually use any data protected by it.
The functions that need to hold the cfg80211_mutex
are the ones using the cfg80211_regdomain variable,
so add the lock assertion to those and clarify this
in the comments.

The reason for this is that nl80211 uses the regdom
without being able to hold reg_mutex.

Acked-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
net/wireless/reg.c