Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752134AbdLLDXT (ORCPT ); Mon, 11 Dec 2017 22:23:19 -0500 Received: from mail-pg0-f68.google.com ([74.125.83.68]:33284 "EHLO mail-pg0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751554AbdLLDXR (ORCPT ); Mon, 11 Dec 2017 22:23:17 -0500 X-Google-Smtp-Source: ACJfBovemwubIaR2pJC4EP6XStCAn6Nwr7zPr7/YQVB70bzc1q/LqPhd1rXOmBb6URV/ecjXn5kRsw== To: ok@artecdesign.ee, Greg KH Cc: Linux Kernel Mailing List , linux-usb@vger.kernel.org From: Jia-Ju Bai Subject: [BUG] drivers/usb/host/isp116x-hcd: a possible sleep-in-atomic bug in isp116x_start Message-ID: Date: Tue, 12 Dec 2017 11:23:06 +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 List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 478 Lines: 17 According to drivers/usb/host/isp116x-hcd.c, the kernel module may sleep under a spinlock. The function call path is: isp116x_start (acquire the spinlock) device_init_wakeup device_wakeup_enable wakeup_source_register wakeup_source_create kmalloc(GFP_KERNEL) --> 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