[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5fbe17917c344f318c25a688f2e94823@SC-EXCH02.marvell.com>
Date: Mon, 3 Sep 2018 06:41:50 +0000
From: Ganapathi Bhat <gbhat@...vell.com>
To: Jia-Ju Bai <baijiaju1990@...il.com>,
"amitkarwar@...il.com" <amitkarwar@...il.com>,
"nishants@...vell.com" <nishants@...vell.com>,
"huxinming820@...il.com" <huxinming820@...il.com>,
"kvalo@...eaurora.org" <kvalo@...eaurora.org>
CC: "linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: RE: [EXT] [BUG] net: wireless: mwifiex: A possible
sleep-in-atomic-context bug in mwifiex_wait_queue_complete()
Hi Jia-Ju,
>
> [FUNC] schedule_timeout
> drivers/net/wireless/marvell/mwifiex/sta_ioctl.c, 63:
> schedule_timeout in mwifiex_wait_queue_complete
> drivers/net/wireless/marvell/mwifiex/cmdevt.c, 673:
> mwifiex_wait_queue_complete in mwifiex_send_cmd
Here, mwifiex_send_cmd does not call mwifiex_wait_queue_complete, because the sync parameter is false.
Note that the function mwifiex_multi_chan_resync did call mwifiex_send_cmd with sync = false.
> drivers/net/wireless/marvell/mwifiex/main.c, 1046:
> mwifiex_send_cmd in mwifiex_multi_chan_resync
> drivers/net/wireless/marvell/mwifiex/usb.c, 288:
> mwifiex_multi_chan_resync in mwifiex_usb_tx_complete
>
Thanks,
Ganapathi
Powered by blists - more mailing lists