Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751729AbdLLIxs (ORCPT ); Tue, 12 Dec 2017 03:53:48 -0500 Received: from mail-it0-f67.google.com ([209.85.214.67]:40725 "EHLO mail-it0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750731AbdLLIxp (ORCPT ); Tue, 12 Dec 2017 03:53:45 -0500 X-Google-Smtp-Source: ACJfBotNqO5THmZANKz/6n5S7LJCKAj3gPlaZxhEsh3QXij2UMZvAHKZAw9yLlf6XGcqVmZkzDfxFQ== To: davem@davemloft.net, keescook@chromium.org, dhowells@redhat.com, timofeev@granch.ru Cc: netdev@vger.kernel.org, Linux Kernel Mailing List From: Jia-Ju Bai Subject: [BUG] sbni: a possible sleep-in-atomic bug in sbni_close Message-ID: <571ba417-9419-5e60-db59-aa642a7e9450@gmail.com> Date: Tue, 12 Dec 2017 16:53:32 +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: 332 Lines: 12 According to drivers/net/wan/sbni.c, the driver may sleep under a spinlock. The function call path is: sbni_close (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