[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3ecba946-7656-3f86-df81-c0b5aff2e3d3@gmail.com>
Date: Mon, 3 Sep 2018 15:35:23 +0800
From: Jia-Ju Bai <baijiaju1990@...il.com>
To: Ganapathi Bhat <gbhat@...vell.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()
On 2018/9/3 14:41, Ganapathi Bhat wrote:
> 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.
Thanks for the reply.
I check the code again, and find my report it false, sorry for that.
Best wishes,
Jia-Ju Bai
Powered by blists - more mailing lists