From: Florian Fainelli <f.fainelli@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>, David Miller <davem@davemloft.net>
Cc: netdev <netdev@vger.kernel.org>,
Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Subject: Re: [PATCH net-next] net: phy: mdio-boardinfo: Allow recursive mdiobus_register()
Date: Wed, 18 Apr 2018 17:14:36 -0700 [thread overview]
Message-ID: <5966673b-f091-a180-71b1-96d35f845e17@gmail.com> (raw)
In-Reply-To: <1524096047-16823-1-git-send-email-andrew@lunn.ch>
On 04/18/2018 05:00 PM, Andrew Lunn wrote:
> mdiobus_register will search for any mdiobus board info registered for
> the bus being registered. If found, it will probe devices on the bus.
> That device, if for example it is an ethernet switch, may then try to
> register an mdio bus. Thus we need to allow recursive calls to
> mdiobus_register.
>
> Holding the mdio_board_lock will cause a deadlock during this
> recursion. Release the lock and use list_for_each_entry_safe.
>
> Signed-off-by: Andrew Lunn <andrew@lunn.ch>
> ---
> drivers/net/phy/mdio-boardinfo.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/phy/mdio-boardinfo.c b/drivers/net/phy/mdio-boardinfo.c
> index 1861f387820d..863496fa5d13 100644
> --- a/drivers/net/phy/mdio-boardinfo.c
> +++ b/drivers/net/phy/mdio-boardinfo.c
> @@ -30,17 +30,20 @@ void mdiobus_setup_mdiodev_from_board_info(struct mii_bus *bus,
> struct mdio_board_info *bi))
> {
> struct mdio_board_entry *be;
> + struct mdio_board_entry *tmp;
> struct mdio_board_info *bi;
> int ret;
>
> mutex_lock(&mdio_board_lock);
Don't you need to drop that lock here?
> - list_for_each_entry(be, &mdio_board_list, list) {
> + list_for_each_entry_safe(be, tmp, &mdio_board_list, list) {
> bi = &be->board_info;
>
> if (strcmp(bus->id, bi->bus_id))
> continue;
>
> + mutex_unlock(&mdio_board_lock);
> ret = cb(bus, bi);
> + mutex_lock(&mdio_board_lock);
> if (ret)
> continue;
>
And conversely drop the unlock from the end of this function?
Also, would you rather target "net" for this change since this appears
to be a bug fix?
--
Florian
next prev parent reply other threads:[~2018-04-19 0:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 0:00 [PATCH net-next] net: phy: mdio-boardinfo: Allow recursive mdiobus_register() Andrew Lunn
2018-04-19 0:14 ` Florian Fainelli [this message]
2018-04-19 0:33 ` Andrew Lunn
2018-04-20 14:34 ` David Miller
2018-04-20 21:59 ` Andrew Lunn
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=5966673b-f091-a180-71b1-96d35f845e17@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@savoirfairelinux.com \
/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).