From: Bastien Nocera <hadess@hadess.net>
To: linux-usb@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alan Stern <stern@rowland.harvard.edu>
Subject: [PATCH v4] USB: Fix device driver race
Date: Fri, 24 Jul 2020 10:59:39 +0200 [thread overview]
Message-ID: <ee32a093d43fe6631617c203ea7c86cb700ceac5.camel@hadess.net> (raw)
When a new device with a specialised device driver is plugged in, the
new driver will be modprobe()'d but the driver core will attach the
"generic" driver to the device.
After that, nothing will trigger a reprobe when the modprobe()'d device
driver has finished initialising, as the device has the "generic"
driver attached to it.
Trigger a reprobe ourselves when new specialised drivers get registered.
Fixes: 88b7381a939d
Signed-off-by: Bastien Nocera <hadess@hadess.net>
---
Changes since v3:
- Only reprobe devices that could use the new driver
- Many code fixes
Changes since v2:
- Fix formatting
Changes since v1:
- Simplified after Alan Stern's comments and some clarifications from
Benjamin Tissoires.
drivers/usb/core/driver.c | 32 ++++++++++++++++++++++++++++++--
1 file changed, 30 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/core/driver.c b/drivers/usb/core/driver.c
index f81606c6a35b..6731a8e104bc 100644
--- a/drivers/usb/core/driver.c
+++ b/drivers/usb/core/driver.c
@@ -905,6 +905,27 @@ static int usb_uevent(struct device *dev, struct kobj_uevent_env *env)
return 0;
}
+static int __usb_bus_reprobe_drivers(struct device *dev, void *data)
+{
+ struct usb_device_driver *new_udriver = data;
+ struct usb_device_driver *udriver;
+ struct usb_device *udev;
+
+ if (!dev->driver)
+ return 0;
+
+ udriver = to_usb_device_driver(dev->driver);
+ if (udriver != &usb_generic_driver)
+ return 0;
+
+ udev = to_usb_device(dev);
+ if (usb_device_match_id(udev, new_udriver->id_table) != NULL ||
+ (new_udriver->match && new_udriver->match(udev) == 0))
+ device_reprobe(dev);
+
+ return 0;
+}
+
/**
* usb_register_device_driver - register a USB device (not interface) driver
* @new_udriver: USB operations for the device driver
@@ -934,13 +955,20 @@ int usb_register_device_driver(struct usb_device_driver *new_udriver,
retval = driver_register(&new_udriver->drvwrap.driver);
- if (!retval)
+ if (!retval) {
pr_info("%s: registered new device driver %s\n",
usbcore_name, new_udriver->name);
- else
+ /* Check whether any device could be better served with
+ * this new driver
+ */
+ if (new_udriver->match || new_udriver->id_table)
+ bus_for_each_dev(&usb_bus_type, NULL, new_udriver,
+ __usb_bus_reprobe_drivers);
+ } else {
printk(KERN_ERR "%s: error %d registering device "
" driver %s\n",
usbcore_name, retval, new_udriver->name);
+ }
return retval;
}
next reply other threads:[~2020-07-24 8:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 8:59 Bastien Nocera [this message]
2020-07-24 10:18 ` [PATCH v4] USB: Fix device driver race Sergei Shtylyov
2020-07-24 15:16 ` Bastien Nocera
2020-07-24 10:32 ` Andy Shevchenko
2020-07-24 10:39 ` Andy Shevchenko
2020-07-24 15:19 ` Bastien Nocera
2020-07-24 15:19 ` Bastien Nocera
2020-07-24 15:27 ` Alan Stern
2020-07-24 16:52 ` Bastien Nocera
2020-07-24 17:08 ` Alan Stern
2020-07-24 17:14 ` Bastien Nocera
2020-07-25 9:17 ` Bastien Nocera
2020-07-24 20:05 ` Andy Shevchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ee32a093d43fe6631617c203ea7c86cb700ceac5.camel@hadess.net \
--to=hadess@hadess.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox