All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>, Jakub Kicinski <kuba@kernel.org>,
	David Miller <davem@davemloft.net>,
	Realtek linux nic maintainers <nic_swsd@realtek.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net] r8169: fix LED-related deadlock on module removal
Date: Fri, 5 Apr 2024 22:59:03 +0200	[thread overview]
Message-ID: <20240405205903.GA3458@wunner.de> (raw)
In-Reply-To: <bbcdbc1b-44bc-4cf8-86ef-6e6af2b009c3@gmail.com>

On Fri, Apr 05, 2024 at 10:29:15PM +0200, Heiner Kallweit wrote:
> --- a/drivers/net/ethernet/realtek/r8169_leds.c
> +++ b/drivers/net/ethernet/realtek/r8169_leds.c
> @@ -146,13 +146,12 @@ static void rtl8168_setup_ldev(struct r8169_led_classdev *ldev,
>  	led_cdev->hw_control_get_device = r8169_led_hw_control_get_device;
>  
>  	/* ignore errors */
> -	devm_led_classdev_register(&ndev->dev, led_cdev);
> +	devm_led_classdev_register(ndev->dev.parent, led_cdev);

IIUC, devm_led_classdev_register() uses the first argument both
to manage unregistering on unbind, but also as parent of the LED device.

While the former is desired, the latter likely is not.
I assume the LEDs now appear as children of the PCI device in sysfs,
not as children of the netdev.  Probably not what you want.

The second patch I posted should handle that correctly.

Thanks,

Lukas

  parent reply	other threads:[~2024-04-05 21:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05 20:29 [PATCH net] r8169: fix LED-related deadlock on module removal Heiner Kallweit
2024-04-05 20:50 ` Andrew Lunn
2024-04-05 20:59 ` Lukas Wunner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-15  6:44 Heiner Kallweit
2024-04-15  8:49 ` Lukas Wunner
2024-04-15 11:54   ` Heiner Kallweit
2024-04-16 23:41   ` Jakub Kicinski
2024-04-17  7:26     ` Lukas Wunner
2024-04-15 11:57 Heiner Kallweit
2024-04-17  2:34 ` Jakub Kicinski
2024-04-17  6:02   ` Heiner Kallweit
2024-04-17  7:04     ` Greg KH
2024-04-17  7:16       ` Heiner Kallweit
2024-04-17  7:43         ` Greg KH
2024-04-17 22:33           ` Lukas Wunner
2024-04-18  9:55             ` Greg KH
2024-04-18 14:33               ` Heiner Kallweit
2024-04-18 14:44                 ` Greg KH
2024-04-17 13:45     ` Jakub Kicinski

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=20240405205903.GA3458@wunner.de \
    --to=lukas@wunner.de \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nic_swsd@realtek.com \
    --cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.