mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oleksij Rempel <o.rempel@pengutronix.de>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: Andrew Lunn <andrew@lunn.ch>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	kernel@pengutronix.de, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 1/1] net: phy: Clear link-specific data on link down
Date: Fri, 22 Aug 2025 11:29:01 +0200	[thread overview]
Message-ID: <aKg4XcM0vAIS4C-8@pengutronix.de> (raw)
In-Reply-To: <aKg2HHIBAR8t2CQW@shell.armlinux.org.uk>

On Fri, Aug 22, 2025 at 10:19:24AM +0100, Russell King (Oracle) wrote:
> On Fri, Aug 22, 2025 at 11:09:47AM +0200, Oleksij Rempel wrote:
> > When a network interface is brought down, the associated PHY is stopped.
> > However, several link-specific parameters within the phy_device struct
> > are not cleared. This leads to userspace tools like ethtool reporting
> > stale information from the last active connection, which is misleading
> > as the link is no longer active.
> 
> This is not a good idea. Consider the case where the PHY has been
> configured with autoneg disabled, and phydev->speed etc specifies
> the desired speed.
> 
> When the link goes down, all that state gets cleared, and we lose
> the user's settings.
> 
> So no, I don't think this is appropriate.
> 
> I think it is appropriate to clear some of the state, but anything that
> the user can configure (such as ->speed and ->duplex) must not be
> cleared.

Hm... should it be cleared conditionally? If autoneg is used, clear the
speed and duplex?

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2025-08-22  9:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-22  9:09 Oleksij Rempel
2025-08-22  9:19 ` Russell King (Oracle)
2025-08-22  9:29   ` Oleksij Rempel [this message]
2025-08-22  9:42     ` Russell King (Oracle)

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=aKg4XcM0vAIS4C-8@pengutronix.de \
    --to=o.rempel@pengutronix.de \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --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 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®