From: Greg KH <gregkh@linuxfoundation.org>
To: Lukas Wunner <lukas@wunner.de>
Cc: Heiner Kallweit <hkallweit1@gmail.com>,
Jakub Kicinski <kuba@kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net] r8169: fix LED-related deadlock on module removal
Date: Thu, 18 Apr 2024 11:55:29 +0200 [thread overview]
Message-ID: <2024041800-yelp-grimy-1819@gregkh> (raw)
In-Reply-To: <ZiBOHF24EDoaI9gm@wunner.de>
On Thu, Apr 18, 2024 at 12:33:00AM +0200, Lukas Wunner wrote:
> On Wed, Apr 17, 2024 at 09:43:27AM +0200, Greg KH wrote:
> > On Wed, Apr 17, 2024 at 09:16:04AM +0200, Heiner Kallweit wrote:
> > > On 17.04.2024 09:04, Greg KH wrote:
> > > > On Wed, Apr 17, 2024 at 08:02:31AM +0200, Heiner Kallweit wrote:
> > > >> On 17.04.2024 04:34, Jakub Kicinski wrote:
> > > >>> On Mon, 15 Apr 2024 13:57:17 +0200 Heiner Kallweit wrote:
> > > >>>> Binding devm_led_classdev_register() to the netdev is problematic
> > > >>>> because on module removal we get a RTNL-related deadlock. Fix this
> > > >>>> by avoiding the device-managed LED functions.
> > > >>>>
> > > >>>> Note: We can safely call led_classdev_unregister() for a LED even
> > > >>>> if registering it failed, because led_classdev_unregister() detects
> > > >>>> this and is a no-op in this case.
> > > >>>>
> > > >>>> Fixes: 18764b883e15 ("r8169: add support for LED's on RTL8168/RTL8101")
> > > >>>> Cc: <stable@vger.kernel.org> # 6.8.x
> > > >>>> Reported-by: Lukas Wunner <lukas@wunner.de>
> > > >>>> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
> > > >>
> > > >> This is a version of the fix modified to apply on 6.8.
> > > >
> > > > That was not obvious at all :(
> > > >
> > > Stating "Cc: <stable@vger.kernel.org> # 6.8.x" isn't sufficient?
> >
> > Without showing what commit id this is in Linus's tree, no.
>
> The upstream commit id *is* called out in the patch, but it's buried
> below the three dashes:
>
> The original change was introduced with 6.8, 6.9 added support for
> LEDs on RTL8125. Therefore the first version of the fix applied on
> 6.9-rc only. This is the modified version for 6.8.
> Upstream commit: 19fa4f2a85d7
> ^^^^^^^^^^^^
>
> The proper way to do this is to prominently add ...
>
> commit 19fa4f2a85d777a8052e869c1b892a2f7556569d upstream.
>
> ... or ...
>
> [ Upstream commit 19fa4f2a85d777a8052e869c1b892a2f7556569d ]
>
> ... as the first line of the commit message, as per
> Documentation/process/stable-kernel-rules.rst
>
Yes, Heiner, please resubmit this, AND submit the fix-for-this-fix as
well, so that if we take this patch, it is not broken.
thanks,
greg k-hj
next prev parent reply other threads:[~2024-04-18 9:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 11:57 [PATCH net] r8169: fix LED-related deadlock on module removal 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 [this message]
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=2024041800-yelp-grimy-1819@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=lukas@wunner.de \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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