diff options
| author |  Vladimir Oltean <vladimir.oltean@nxp.com>
| 2022-02-07 18:15:52 +0200 |
|---|---|---|
| committer |  Jakub Kicinski <kuba@kernel.org>
| 2022-02-08 20:30:35 -0800 |
| commit | 9ffe3d09e32da45bb5a29cf2e80ec8d7534010c5 (patch) | |
| tree | 8d6fca6d198f310259ccbe73a1879676ef5cfa1d /drivers/net/dsa/lantiq_gswip.c | |
| parent | net: dsa: seville: register the mdiobus under devres (diff) | |
| download | linux-9ffe3d09e32da45bb5a29cf2e80ec8d7534010c5.tar.gz linux-9ffe3d09e32da45bb5a29cf2e80ec8d7534010c5.tar.bz2 linux-9ffe3d09e32da45bb5a29cf2e80ec8d7534010c5.zip | |
net: dsa: mt7530: fix kernel bug in mdiobus_free() when unbinding
Nobody in this driver calls mdiobus_unregister(), which is necessary if
mdiobus_register() completes successfully. So if the devres callbacks
that free the mdiobus get invoked (this is the case when unbinding the
driver), mdiobus_free() will BUG if the mdiobus is still registered,
which it is.
My speculation is that this is due to the fact that prior to commit
ac3a68d56651 ("net: phy: don't abuse devres in devm_mdiobus_register()")
from June 2020, _devm_mdiobus_free() used to call mdiobus_unregister().
But at the time that the mt7530 support was introduced in May 2021, the
API was already changed. It's therefore likely that the blamed patch was
developed on an older tree, and incorrectly adapted to net-next. This
makes the Fixes: tag correct.
Fix the problem by using the devres variant of mdiobus_register.
Fixes: ba751e28d442 ("net: dsa: mt7530: add interrupt support")
Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'drivers/net/dsa/lantiq_gswip.c')
0 files changed, 0 insertions, 0 deletions