From: Jia-Ju Bai <baijiaju1990@gmail.com>
Subject: [BUG] wl3501: a possible sleep-in-atomic bug in wl3501_reset
To: kvalo@codeaurora.org, mhchen@golf.ccl.itri.org.tw,
        acme@conectiva.com.br, niemeyer@conectiva.com
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
        linux-kernel@vger.kernel.org
Message-ID: <8b0519f9-e5f3-aa73-09be-f399f6a6865a@gmail.com>
Date: Tue, 12 Dec 2017 17:04:52 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.2.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 345
Lines: 13

According to drivers/net/wireless/wl3501_cs.c, the driver may sleep 
under a spinlock.
The function call path is:
wl3501_reset (acquire the spinlock)
   free_irq --> may sleep

I do not find a good way to fix it, so I only report.
This possible bug is found by my static analysis tool (DSAC) and checked 
by my code review.


Thanks,
Jia-Ju Bai