cfg80211: always shut down on HW rfkill
authorJohannes Berg <johannes.berg@intel.com>
Fri, 30 Aug 2019 11:24:44 +0000 (14:24 +0300)
committerJohannes Berg <johannes.berg@intel.com>
Wed, 11 Sep 2019 07:13:26 +0000 (09:13 +0200)
commit3cfe91c4c3c080c6af95611a87f8cf32d1913896
treecb37ec244f749f948a4dda98dc7cb13bdb75dcd7
parente5c0b0fff6b19238eb0f33ec58247db3e5295cdd
cfg80211: always shut down on HW rfkill

When the RFKILL subsystem isn't available, then rfkill_blocked()
always returns false. In the case of hardware rfkill this will
be wrong though, as if the hardware reported being killed then
it cannot operate any longer.

Since we only ever call the rfkill_sync work in this case, just
rename it to rfkill_block and always pass "true" for the blocked
parameter, rather than passing rfkill_blocked().

We rely on the underlying driver to still reject any new attempt
to bring up the device by itself.

Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
Link: https://lore.kernel.org/r/20190830112451.21655-2-luca@coelho.fi
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
net/wireless/core.c
net/wireless/core.h
net/wireless/wext-compat.c