From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bastien Nocera <hadess@hadess.net>
Cc: linux-usb@vger.kernel.org, Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [PATCH 1/2] USB: Fix device driver race
Date: Wed, 22 Jul 2020 13:12:33 +0200 [thread overview]
Message-ID: <20200722111233.GA2912795@kroah.com> (raw)
In-Reply-To: <20200722094628.4236-1-hadess@hadess.net>
On Wed, Jul 22, 2020 at 11:46:27AM +0200, Bastien Nocera 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.
>
> Signed-off-by: Bastien Nocera <hadess@hadess.net>
> ---
What commit id does this fix? And if it's in an older kernel, should it
be backported to the stable trees?
thanks,
greg k-h
next prev parent reply other threads:[~2020-07-22 11:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 9:46 [PATCH 1/2] USB: Fix device driver race Bastien Nocera
2020-07-22 9:46 ` [PATCH 2/2] USB: Fix source path in header Bastien Nocera
2020-07-22 9:51 ` Greg Kroah-Hartman
2020-07-22 9:58 ` Bastien Nocera
2020-07-22 10:35 ` Greg Kroah-Hartman
2020-07-22 10:56 ` Bastien Nocera
2020-07-22 11:12 ` Greg Kroah-Hartman [this message]
2020-07-22 11:18 ` [PATCH 1/2] USB: Fix device driver race Bastien Nocera
2020-07-22 15:26 ` Alan Stern
2020-07-22 15:53 ` Bastien Nocera
2020-07-23 2:19 ` Peter Chen
2020-07-23 9:02 ` Bastien Nocera
2020-07-23 10:35 ` Peter Chen
2020-07-23 10:49 ` Greg Kroah-Hartman
2020-07-23 10:57 ` Bastien Nocera
2020-07-23 12:12 ` Peter Chen
2020-07-23 12:14 ` Bastien Nocera
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=20200722111233.GA2912795@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=hadess@hadess.net \
--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