forked from Minki/linux
98743f8749
ieee80211_ccmp_init() is never called in atomic context. ieee80211_ccmp_init() is only set as ".init" in struct ieee80211_crypto_ops. The call chains ending up at "->init" function are: [1] ->init() <- ieee80211_wpa_set_encryption() <- ieee80211_wpa_supplicant_ioctl() [2] ->init() <- ieee80211_wx_set_encode_ext_rsl() <- r8192_wx_set_enc_ext() [3] ->init() <- ieee80211_wx_set_encode_rsl() <- r8192_wx_set_enc() ieee80211_wpa_supplicant_ioctl(), r8192_wx_set_enc_ext() and r8192_wx_set_enc() call mutex_lock(), which indicates these functions are not called in atomic context. Despite never getting called from atomic context, ieee80211_ccmp_init() calls kzalloc() with GFP_ATOMIC, which does not sleep for allocation. GFP_ATOMIC is not necessary and can be replaced with GFP_KERNEL, which can sleep and improve the possibility of sucessful allocation. This is found by a static analysis tool named DCNS written by myself. And I also manually check it. Signed-off-by: Jia-Ju Bai <baijiaju1990@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
||
---|---|---|
.. | ||
ieee80211 | ||
authors | ||
changes | ||
copying | ||
Kconfig | ||
Makefile | ||
r819xU_cmdpkt.c | ||
r819xU_cmdpkt.h | ||
r819xU_firmware_img.c | ||
r819xU_firmware_img.h | ||
r819xU_firmware.c | ||
r819xU_firmware.h | ||
r819xU_phy.c | ||
r819xU_phy.h | ||
r819xU_phyreg.h | ||
r8180_93cx6.c | ||
r8180_93cx6.h | ||
r8190_rtl8256.c | ||
r8190_rtl8256.h | ||
r8192U_core.c | ||
r8192U_dm.c | ||
r8192U_dm.h | ||
r8192U_hw.h | ||
r8192U_wx.c | ||
r8192U_wx.h | ||
r8192U.h |