On Tue, Oct 18, 2022 at 04:34:24PM +0800, Duoming Zhou wrote: > The rtw_join_timeout_handler() is a timer handler that > runs in atomic context, but it could call msleep(). > As a result, the sleep-in-atomic-context bug will happen. > The process is shown below: > > (atomic context) > rtw_join_timeout_handler Wait, how is this an atomic timeout? When can that happen? > _rtw_join_timeout_handler > rtw_do_join > rtw_select_and_join_from_scanned_queue > rtw_indicate_disconnect > rtw_lps_ctrl_wk_cmd > lps_ctrl_wk_hdl > LPS_Leave > LPS_RF_ON_check > msleep //sleep in atomic context How was this found? > Fix by removing msleep() and replacing with mdelay(). Wouldn't people have seen an error already if msleep() was really called in atomic context? And what about the other drivers that have this identical code, why only fix one? thanks, greg k-h
