From: Andrew Lunn <andrew@lunn.ch>
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Florian Fainelli <f.fainelli@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Daniel Golle <daniel@makrotopia.org>,
stable@vger.kernel.org
Subject: Re: [net PATCH 1/2] net: phy: Remove LED entry from LEDs list on unregister
Date: Fri, 4 Oct 2024 00:45:10 +0200 [thread overview]
Message-ID: <f6e1eaf5-4d49-4394-a2e7-d739d7991d2f@lunn.ch> (raw)
In-Reply-To: <20241003221006.4568-1-ansuelsmth@gmail.com>
On Fri, Oct 04, 2024 at 12:10:04AM +0200, Christian Marangi wrote:
> Commit c938ab4da0eb ("net: phy: Manual remove LEDs to ensure correct
> ordering") correctly fixed a problem with using devm_ but missed
> removing the LED entry from the LEDs list.
>
> This cause kernel panic on specific scenario where the port for the PHY
> is torn down and up and the kmod for the PHY is removed.
>
> On setting the port down the first time, the assosiacted LEDs are
> correctly unregistered. The associated kmod for the PHY is now removed.
> The kmod is now added again and the port is now put up, the associated LED
> are registered again.
> On putting the port down again for the second time after these step, the
> LED list now have 4 elements. With the first 2 already unregistered
> previously and the 2 new one registered again.
>
> This cause a kernel panic as the first 2 element should have been
> removed.
>
> Fix this by correctly removing the element when LED is unregistered.
>
> Reported-by: Daniel Golle <daniel@makrotopia.org>
> Tested-by: Daniel Golle <daniel@makrotopia.org>
> Cc: stable@vger.kernel.org
> Fixes: c938ab4da0eb ("net: phy: Manual remove LEDs to ensure correct ordering")
> Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
prev parent reply other threads:[~2024-10-03 22:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 22:10 Christian Marangi
2024-10-03 22:10 ` [net PATCH 2/2] net: phy: Skip PHY LEDs OF registration for Generic PHY driver Christian Marangi
2024-10-03 22:50 ` Andrew Lunn
2024-10-04 9:13 ` Christian Marangi
2024-10-04 13:44 ` Andrew Lunn
2024-10-04 13:46 ` Christian Marangi
2024-10-04 14:11 ` Andrew Lunn
2024-10-04 14:12 ` Christian Marangi
2024-10-03 22:45 ` Andrew Lunn [this message]
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=f6e1eaf5-4d49-4394-a2e7-d739d7991d2f@lunn.ch \
--to=andrew@lunn.ch \
--cc=ansuelsmth@gmail.com \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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
all inboxes | Powered by JetHome®