[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <9c242f84-367e-d857-24a6-8336d652257c@i2se.com>
Date: Wed, 11 Jan 2023 18:15:40 +0100
From: Stefan Wahren <stefan.wahren@...e.com>
To: Matthias Kaehlcke <mka@...omium.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Icenowy Zheng <uwu@...nowy.me>, stable@...r.kernel.org,
Alexander Stein <alexander.stein@...tq-group.com>,
linux-usb@...r.kernel.org, Johan Hovold <johan@...nel.org>,
linux-kernel@...r.kernel.org,
Douglas Anderson <dianders@...omium.org>,
Ravi Chandra Sadineni <ravisadineni@...omium.org>
Subject: Re: [PATCH v2 1/2] usb: misc: onboard_hub: Invert driver registration
order
Hi Matthias,
Am 10.01.23 um 18:32 schrieb Matthias Kaehlcke:
> The onboard_hub 'driver' consists of two drivers, a platform
> driver and a USB driver. Currently when the onboard hub driver
> is initialized it first registers the platform driver, then the
> USB driver. This results in a race condition when the 'attach'
> work is executed, which is scheduled when the platform device
> is probed. The purpose of fhe 'attach' work is to bind elegible
> USB hub devices to the onboard_hub USB driver. This fails if
> the work runs before the USB driver has been registered.
>
> Register the USB driver first, then the platform driver. This
> increases the chances that the onboard_hub USB devices are probed
> before their corresponding platform device, which the USB driver
> tries to locate in _probe(). The driver already handles this
> situation and defers probing if the onboard hub platform device
> doesn't exist yet.
>
> Cc: stable@...r.kernel.org
> Fixes: 8bc063641ceb ("usb: misc: Add onboard_usb_hub driver")
> Link: https://lore.kernel.org/lkml/Y6W00vQm3jfLflUJ@hovoldconsulting.com/T/#m0d64295f017942fd988f7c53425db302d61952b4
> Reported-by: Alexander Stein <alexander.stein@...tq-group.com>
> Signed-off-by: Matthias Kaehlcke <mka@...omium.org>
the whole series is:
Tested-by: Stefan Wahren <stefan.wahren@...e.com>
Thanks \o/
Powered by blists - more mailing lists