From: Pavan Chebbi <pavan.chebbi@broadcom.com>
To: Thomas Bogendoerfer <tbogendoerfer@suse.de>
Cc: Michael Chan <mchan@broadcom.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
Nithin Sujir <nsujir@broadcom.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] tg3: Fix race for querying speed/duplex
Date: Thu, 26 Mar 2026 15:29:08 +0530 [thread overview]
Message-ID: <CALs4sv1qp7Gz-WsuNj-zvx2z=kRFLqxQnn-iUpwj0pTirBCydg@mail.gmail.com> (raw)
In-Reply-To: <20260325112054.108988-1-tbogendoerfer@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1544 bytes --]
On Wed, Mar 25, 2026 at 4:51 PM Thomas Bogendoerfer
<tbogendoerfer@suse.de> wrote:
>
> When driver signals carrier up via netif_carrier_on() its internal
> link_up state isn't updated immediately. This leads to inconsistent
> speed/duplex in /proc/net/bonding/bondX where the speed and duplex
> is shown as unknown while ethtool shows correct values. Fix this by
> using netif_carrier_ok() for link checking in get_ksettings function.
>
> Fixes: 84421b99cedc ("tg3: Update link_up flag for phylib devices")
> Signed-off-by: Thomas Bogendoerfer <tbogendoerfer@suse.de>
> ---
> drivers/net/ethernet/broadcom/tg3.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Reviewed-by: Pavan Chebbi <pavan.chebbi@broadcom.com>
Thank you.
> diff --git a/drivers/net/ethernet/broadcom/tg3.c b/drivers/net/ethernet/broadcom/tg3.c
> index 21a5dd342724..73a4b569b03e 100644
> --- a/drivers/net/ethernet/broadcom/tg3.c
> +++ b/drivers/net/ethernet/broadcom/tg3.c
> @@ -12299,7 +12299,7 @@ static int tg3_get_link_ksettings(struct net_device *dev,
> ethtool_convert_legacy_u32_to_link_mode(cmd->link_modes.advertising,
> advertising);
>
> - if (netif_running(dev) && tp->link_up) {
> + if (netif_running(dev) && netif_carrier_ok(dev)) {
> cmd->base.speed = tp->link_config.active_speed;
> cmd->base.duplex = tp->link_config.active_duplex;
> ethtool_convert_legacy_u32_to_link_mode(
> --
> 2.43.0
>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5469 bytes --]
prev parent reply other threads:[~2026-03-26 9:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 11:20 [PATCH net] tg3: Fix race for querying speed/duplex Thomas Bogendoerfer
2026-03-26 9:59 ` Pavan Chebbi [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='CALs4sv1qp7Gz-WsuNj-zvx2z=kRFLqxQnn-iUpwj0pTirBCydg@mail.gmail.com' \
--to=pavan.chebbi@broadcom.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=nsujir@broadcom.com \
--cc=pabeni@redhat.com \
--cc=tbogendoerfer@suse.de \
/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