Netdev List
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Yongzhao Chen <yongzhao.derek@gmail.com>
Cc: netdev@vger.kernel.org, Christian Marangi <ansuelsmth@gmail.com>,
	Vladimir Oltean <olteanv@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@kernel.org>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	John Crispin <john@phrozen.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 3/3] net: dsa: qca8k: fail mgmt Ethernet MDIO access on busy wait errors
Date: Mon, 5 Oct 2026 19:07:24 +0200	[thread overview]
Message-ID: <acbcea38-30e5-4aba-908a-7ff986bc4da0@lunn.ch> (raw)
In-Reply-To: <20261003172405.342-4-yongzhao.derek@gmail.com>

On Sat, Oct 03, 2026 at 07:24:04PM +0200, Yongzhao Chen wrote:
> qca8k_phy_eth_command() polls MASTER_CTRL over management Ethernet until
> BUSY clears, but only bails out when the poll timed out and the last
> poll request also failed. If every request succeeds while BUSY stays
> set, the -ETIMEDOUT is dropped. A read then returns MASTER_CTRL data
> from a transaction that has not completed, and
> qca8k_internal_mdio_read() does not fall back to the MDIO bus.
> 
> A failed poll request does not stop the loop either.
> qca8k_phy_eth_busy_wait() leaves the value unchanged on failure, so the
> BUSY test then uses the previous value, or an uninitialized one if the
> first request fails.
> 
> Stop polling when a request fails and return the poll error or timeout.
> The poll-error path also leaked read_skb, which is only consumed when the
> read request is sent; free it on this path.
> 
> The Sashiko review of v1 identified the dropped timeout. A userspace
> model of the driver's functions reproduces it and the poll-error path
> with scripted BUSY responses and failed poll requests; these cases pass
> after this change.
> 
> The polling loop comes from commit 2cd548566384 ("net: dsa: qca8k: add
> support for phy read/write with mgmt Ethernet").
> 
> Signed-off-by: Yongzhao Chen <yongzhao.derek@gmail.com>

Reviewed-by: Andrew Lunn <andrew@lunn.ch>

    Andrew

  reply	other threads:[~2026-10-05 17:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-03 17:24 [PATCH net-next v3 0/3] net: dsa: qca8k: fix MDIO error handling Yongzhao Chen
2026-10-03 17:24 ` [PATCH net-next v3 1/3] net: dsa: qca8k: propagate MDIO errors Yongzhao Chen
2026-10-05 17:00   ` Andrew Lunn
2026-10-03 17:24 ` [PATCH net-next v3 2/3] net: dsa: qca8k: do not clear MASTER_EN after a failed page select Yongzhao Chen
2026-10-05 17:06   ` Andrew Lunn
2026-10-03 17:24 ` [PATCH net-next v3 3/3] net: dsa: qca8k: fail mgmt Ethernet MDIO access on busy wait errors Yongzhao Chen
2026-10-05 17:07   ` Andrew Lunn [this message]
2026-10-07  1:00 ` [PATCH net-next v3 0/3] net: dsa: qca8k: fix MDIO error handling patchwork-bot+netdevbpf

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=acbcea38-30e5-4aba-908a-7ff986bc4da0@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ansuelsmth@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=john@phrozen.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=yongzhao.derek@gmail.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