From: Alan Stern <stern@rowland.harvard.edu>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Bastien Nocera <hadess@hadess.net>,
USB <linux-usb@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v4] USB: Fix device driver race
Date: Fri, 24 Jul 2020 11:27:07 -0400 [thread overview]
Message-ID: <20200724152707.GB1388675@rowland.harvard.edu> (raw)
In-Reply-To: <CAHp75VeKY0FSdfza0E9Fz8=2dCyPXwPZYE0kjywiRQAsvmbiow@mail.gmail.com>
On Fri, Jul 24, 2020 at 01:32:40PM +0300, Andy Shevchenko wrote:
> On Fri, Jul 24, 2020 at 12:03 PM Bastien Nocera <hadess@hadess.net> wrote:
> >
> > 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.
>
> ...
>
> > +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;
>
> What about
>
> static bool is_dev_usb_generic_driver(dev)
> {
> struct usb_device_driver *udd = dev->driver ?
> to_usb_device_driver(dev->driver) : NULL;
>
> return udd == &usb_generic_driver;
> }
>
> if (!is_dev_usb_generic_driver)
> return 0;
>
> ?
Why would you want to add more lines of code to do the same thing?
Abstraction is fine up to point, but excessive abstraction only makes
things more difficult.
>
> > + 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;
>
> What about
>
> udev = to_usb_device(dev);
> if (usb_device_match_id(udev, new_udriver->id_table) == NULL)
> return 0;
> ?
The logic is wrong. If usb_device_match_id() returns NULL then we want
to go ahead with the second test, not give up right away. But this
could be written as:
if (usb_device_match_id(udev, new_udriver->id_table) == NULL &&
(!new_udriver->match || new_udriver->match(udev) != 0))
return 0;
device_reprobe(dev);
This would make the overall flow of the routine more uniform.
> > + /* Check whether any device could be better served with
> > + * this new driver
> > + */
>
> Comment style?
Right:
/*
* Multiline comments
* should look like this.
*/
> ...
>
> > + if (new_udriver->match || new_udriver->id_table)
>
> But match check is incorporated in the loop function.
Agreed, this test is redundant. However, we should test that
new_udriver != &usb_generic_driver.
Alan Stern
>
> > + bus_for_each_dev(&usb_bus_type, NULL, new_udriver,
> > + __usb_bus_reprobe_drivers);
>
> --
> With Best Regards,
> Andy Shevchenko
next prev parent reply other threads:[~2020-07-24 15:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 8:59 [PATCH v4] USB: Fix device driver race Bastien Nocera
2020-07-24 10:18 ` 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 [this message]
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=20200724152707.GB1388675@rowland.harvard.edu \
--to=stern@rowland.harvard.edu \
--cc=andy.shevchenko@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hadess@hadess.net \
--cc=linux-usb@vger.kernel.org \
/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