From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jia-Ju Bai <baijiaju1990@gmail.com>
Subject: [BUG] b44: two possible sleep-in-atomic bugs in
 b44_set_link_ksettings and b44_ioctl
Date: Wed, 13 Dec 2017 11:29:46 +0800
Message-ID: <5299283f-95e6-61b5-267c-5e12ca72fe41@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
To: michael.chan@broadcom.com, hauke@hauke-m.de,
        David Miller <davem@davemloft.net>, f.fainelli@gmail.com,
        opendmb@gmail.com, sathya.perla@broadcom.com
Return-path: <linux-kernel-owner@vger.kernel.org>
Content-Language: en-US
Sender: linux-kernel-owner@vger.kernel.org
List-Id: netdev.vger.kernel.org

The driver may sleep under a spinlock.
The function call paths are:
b44_set_link_ksettings (acquire the spinlock)
   phy_ethtool_ksettings_set
     phy_start_aneg
       phy_start_aneg_priv
         mutex_lock --> may sleep

b44_ioctl (acquire the spinlock)
   phy_mii_ioctl
     mdiobus_read
       mutex_lock --> may sleep

I do not find a good way to fix them, so I only report.
These possible bugs are found by my static analysis tool (DSAC) and 
checked by my code review.


Thanks,
Jia-Ju Bai