From: Oliver Neukum <oneukum@suse.com>
To: Lukas Wunner <lukas@wunner.de>, Oliver Neukum <oneukum@suse.com>
Cc: Oleksij Rempel <o.rempel@pengutronix.de>,
Andrew Lunn <andrew@lunn.ch>,
Oleksij Rempel <linux@rempel-privat.de>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Heiner Kallweit <hkallweit1@gmail.com>
Subject: Re: ordering of call to unbind() in usbnet_disconnect
Date: Thu, 31 Mar 2022 11:59:44 +0200 [thread overview]
Message-ID: <8f59f82c-e1eb-f8f5-a646-189c0eac94cf@suse.com> (raw)
In-Reply-To: <20220331093040.GA20035@wunner.de>
On 31.03.22 11:30, Lukas Wunner wrote:
> I propose the below patch. If you could provide more details on the
> regressions you've reported (+ ideally bugzilla links), I'll be happy
> to include them in the commit message. Thanks!
There is no bugzilla, but the report can be found:
https://lore.kernel.org/netdev/CAG48ez0MHBbENX5gCdHAUXZ7h7s20LnepBF-pa5M=7Bi-jZrEA@mail.gmail.com/
>
> The commit made binding and unbinding of USB Ethernet asymmetrical:
> Before, usbnet_probe() first invoked the ->bind() callback and then
> register_netdev(). usbnet_disconnect() mirrored that by first invoking
> unregister_netdev() and then ->unbind().
>
> Since the commit, the order in usbnet_disconnect() is reversed and no
> longer mirrors usbnet_probe().
>
> One consequence is that a PHY disconnected (and stopped) in ->unbind()
> is afterwards stopped once more by unregister_netdev() as it closes the
> netdev before unregistering. That necessitates a contortion in ->stop()
> because the PHY may only be stopped if it hasn't already been
> disconnected.
>
> Reverting the commit allows making the call to phy_stop() unconditional
> in ->stop() and also fixes the issues reported by Oliver.
Very well, but what prevents reintroducing the isssue this revert's
target was to fix?
Regards
Oliver
next prev parent reply other threads:[~2022-03-31 9:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 11:25 ordering of call to unbind() in usbnet_disconnect Oliver Neukum
2022-03-10 11:38 ` Oleksij Rempel
2022-03-14 18:42 ` Lukas Wunner
2022-03-14 19:14 ` Andrew Lunn
2022-03-15 5:44 ` Oleksij Rempel
2022-03-15 8:32 ` Lukas Wunner
2022-03-15 11:38 ` Oleksij Rempel
2022-03-15 13:28 ` Andrew Lunn
2022-03-17 15:53 ` Oliver Neukum
2022-03-17 21:03 ` Lukas Wunner
2022-03-21 10:17 ` Lukas Wunner
2022-03-21 10:43 ` Oleksij Rempel
2022-03-31 9:35 ` Oliver Neukum
2022-03-21 10:02 ` Lukas Wunner
2022-03-21 13:10 ` Andrew Lunn
2022-03-26 12:39 ` Lukas Wunner
2022-03-26 12:49 ` Andrew Lunn
2022-03-26 13:04 ` Lukas Wunner
2022-03-27 8:37 ` Oleksij Rempel
2022-03-31 9:20 ` Oliver Neukum
2022-03-31 9:30 ` Lukas Wunner
2022-03-31 9:59 ` Oliver Neukum [this message]
2022-03-31 11:22 ` Lukas Wunner
2022-03-26 12:25 ` Lukas Wunner
2022-03-26 12:44 ` Andrew Lunn
2022-03-26 13:01 ` Lukas Wunner
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=8f59f82c-e1eb-f8f5-a646-189c0eac94cf@suse.com \
--to=oneukum@suse.com \
--cc=andrew@lunn.ch \
--cc=hkallweit1@gmail.com \
--cc=linux@rempel-privat.de \
--cc=lukas@wunner.de \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).