[PATCH v10 2/5] driver core: don't always lock parent in shutdown
Greg Kroah-Hartman
gregkh at linuxfoundation.org
Tue Jul 1 01:50:28 PDT 2025
On Wed, Jun 25, 2025 at 03:18:50PM -0500, Stuart Hayes wrote:
> Don't lock a parent device unless it is needed in device_shutdown. This
> is in preparation for making device shutdown asynchronous, when it will
> be needed to allow children of a common parent to shut down
> simultaneously.
>
> Signed-off-by: Stuart Hayes <stuart.w.hayes at gmail.com>
> Signed-off-by: David Jeffery <djeffery at redhat.com>
> ---
> drivers/base/core.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/base/core.c b/drivers/base/core.c
> index cbc0099d8ef2..58c772785606 100644
> --- a/drivers/base/core.c
> +++ b/drivers/base/core.c
> @@ -4823,7 +4823,7 @@ void device_shutdown(void)
> spin_unlock(&devices_kset->list_lock);
>
> /* hold lock to avoid race with probe/release */
> - if (parent)
> + if (parent && dev->bus && dev->bus->need_parent_lock)
> device_lock(parent);
What about parents for a device that is not on a bus? Don't they need
to be properly locked?
> device_lock(dev);
>
> @@ -4847,7 +4847,7 @@ void device_shutdown(void)
> }
>
> device_unlock(dev);
> - if (parent)
> + if (parent && dev->bus && dev->bus->need_parent_lock)
> device_unlock(parent);
Same here.
thanks,
greg k-h
More information about the Linux-nvme
mailing list