Revert "drivers: core: synchronize really_probe() and dev_uevent()"

commit dc1771f718 upstream.

This reverts commit c0a40097f0.

Probing a device can take arbitrary long time. In the field we observed
that, for example, probing a bad micro-SD cards in an external USB card
reader (or maybe cards were good but cables were flaky) sometimes takes
longer than 2 minutes due to multiple retries at various levels of the
stack. We can not block uevent_show() method for that long because udev
is reading that attribute very often and that blocks udev and interferes
with booting of the system.

The change that introduced locking was concerned with dev_uevent()
racing with unbinding the driver. However we can handle it without
locking (which will be done in subsequent patch).

There was also claim that synchronization with probe() is needed to
properly load USB drivers, however this is a red herring: the change
adding the lock was introduced in May of last year and USB loading and
probing worked properly for many years before that.

Revert the harmful locking.

Cc: stable@vger.kernel.org
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Reviewed-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Link: https://lore.kernel.org/r/20250311052417.1846985-1-dmitry.torokhov@gmail.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

This commit is contained in:

Dmitry Torokhov

2025-03-10 22:24:14 -07:00

committed by

Greg Kroah-Hartman

parent 185d376875

commit bfc66c4c28

1 changed files with 0 additions and 3 deletions

									
										drivers/base/core.c
									
		-3
	
												View File
												
				@@ -2726,11 +2726,8 @@ static ssize_t uevent_show(struct device *dev, struct device_attribute *attr,

					if (!env)

						return -ENOMEM;

					/* Synchronize with really_probe() */

					device_lock(dev);

					/* let the kset specific function add its keys */

					retval = kset->uevent_ops->uevent(&dev->kobj, env);

					device_unlock(dev);

					if (retval)

						goto out;