driver core: Move device_links_purge() after bus_remove_device()
authorJeffy Chen <jeffy.chen@rock-chips.com>
Fri, 20 Oct 2017 12:01:01 +0000 (20:01 +0800)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sat, 1 Dec 2018 08:42:59 +0000 (09:42 +0100)
commitc8692d9f5ceff240792df5b42ca1639ace77204b
tree1ff15176dc672e0467d9913036eedb821ce12d61
parenta46ca4c8f1c64723ce0a9f66638a1343a71bbe3f
driver core: Move device_links_purge() after bus_remove_device()

commit 2ec16150179888b81717d1d3ce84e634f4736af2 upstream.

The current ordering of code in device_del() triggers a WARN_ON()
in device_links_purge(), because of an unexpected link status.

The device_links_unbind_consumers() call in device_release_driver()
has to take place before device_links_purge() for the status of all
links to be correct, so move the device_links_purge() call in
device_del() after the invocation of bus_remove_device() which calls
device_release_driver().

Fixes: 9ed9895370ae (driver core: Functional dependencies tracking support)
Signed-off-by: Jeffy Chen <jeffy.chen@rock-chips.com>
Reviewed-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Signed-off-by: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/base/core.c