diff options
author | Lukas Wunner <lukas@wunner.de> | 2020-07-08 15:27:01 +0200 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2020-07-30 08:48:34 +0200 |
commit | 654888327e9f655a9d55ad477a9583e90e8c9b5c (patch) | |
tree | 6374ad06215d457cc1db6a57a1ec0a6e3c9aaa74 /include/linux/device.h | |
parent | eea2c51f81df9df5123c042f07c7c6c33bf5fabb (diff) | |
download | lwn-654888327e9f655a9d55ad477a9583e90e8c9b5c.tar.gz lwn-654888327e9f655a9d55ad477a9583e90e8c9b5c.zip |
driver core: Avoid binding drivers to dead devices
Commit 3451a495ef24 ("driver core: Establish order of operations for
device_add and device_del via bitflag") sought to prevent asynchronous
driver binding to a device which is being removed. It added a
per-device "dead" flag which is checked in the following code paths:
* asynchronous binding in __driver_attach_async_helper()
* synchronous binding in device_driver_attach()
* asynchronous binding in __device_attach_async_helper()
It did *not* check the flag upon:
* synchronous binding in __device_attach()
However __device_attach() may also be called asynchronously from:
deferred_probe_work_func()
bus_probe_device()
device_initial_probe()
__device_attach()
So if the commit's intention was to check the "dead" flag in all
asynchronous code paths, then a check is also necessary in
__device_attach(). Add the missing check.
Fixes: 3451a495ef24 ("driver core: Establish order of operations for device_add and device_del via bitflag")
Signed-off-by: Lukas Wunner <lukas@wunner.de>
Cc: stable@vger.kernel.org # v5.1+
Cc: Alexander Duyck <alexander.h.duyck@linux.intel.com>
Link: https://lore.kernel.org/r/de88a23a6fe0ef70f7cfd13c8aea9ab51b4edab6.1594214103.git.lukas@wunner.de
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'include/linux/device.h')
0 files changed, 0 insertions, 0 deletions