From: Mateusz Polchlopek <mateusz.polchlopek@intel.com>
To: Oleksij Rempel <o.rempel@pengutronix.de>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Woojung Huh <woojung.huh@microchip.com>,
Andrew Lunn <andrew+netdev@lunn.ch>
Cc: <kernel@pengutronix.de>, <linux-kernel@vger.kernel.org>,
<netdev@vger.kernel.org>, <UNGLinuxDriver@microchip.com>,
Phil Elwell <phil@raspberrypi.org>
Subject: Re: [PATCH net-next v1 1/6] net: usb: lan78xx: Add error handling to lan78xx_get_regs
Date: Mon, 16 Dec 2024 14:07:37 +0100 [thread overview]
Message-ID: <c7ddac7d-debc-44eb-9c43-7746ad3edb55@intel.com> (raw)
In-Reply-To: <20241216120941.1690908-2-o.rempel@pengutronix.de>
On 12/16/2024 1:09 PM, Oleksij Rempel wrote:
> Update `lan78xx_get_regs` to handle errors during register and PHY
> reads. Log warnings for failed reads and exit the function early if an
> error occurs. Drop all previously logged registers to signal
> inconsistent readings to the user space. This ensures that invalid data
> is not returned to users.
>
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> ---
> drivers/net/usb/lan78xx.c | 36 ++++++++++++++++++++++++++++++------
> 1 file changed, 30 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/net/usb/lan78xx.c b/drivers/net/usb/lan78xx.c
> index 4661d131b190..270345fcad65 100644
> --- a/drivers/net/usb/lan78xx.c
> +++ b/drivers/net/usb/lan78xx.c
> @@ -2108,20 +2108,44 @@ static void
> lan78xx_get_regs(struct net_device *netdev, struct ethtool_regs *regs,
> void *buf)
> {
> - u32 *data = buf;
> - int i, j;
> struct lan78xx_net *dev = netdev_priv(netdev);
> + unsigned int data_count = 0;
> + u32 *data = buf;
> + int i, j, ret;
>
> /* Read Device/MAC registers */
> - for (i = 0; i < ARRAY_SIZE(lan78xx_regs); i++)
> - lan78xx_read_reg(dev, lan78xx_regs[i], &data[i]);
> + for (i = 0; i < ARRAY_SIZE(lan78xx_regs); i++) {
> + ret = lan78xx_read_reg(dev, lan78xx_regs[i], &data[i]);
> + if (ret < 0) {
> + netdev_warn(dev->net,
> + "failed to read register 0x%08x\n",
> + lan78xx_regs[i]);
> + goto clean_data;
> + }
> +
> + data_count++;
> + }
>
> if (!netdev->phydev)
> return;
>
> /* Read PHY registers */
> - for (j = 0; j < 32; i++, j++)
> - data[i] = phy_read(netdev->phydev, j);
> + for (j = 0; j < 32; i++, j++) {
Maybe during this refactor is it worth to add some #define with
number of registers to be read?
> + ret = phy_read(netdev->phydev, j);
> + if (ret < 0) {
> + netdev_warn(dev->net,
> + "failed to read PHY register 0x%02x\n", j);
> + goto clean_data;
> + }
> +
> + data[i] = ret;
> + data_count++;
> + }
> +
> + return;
> +
> +clean_data:
> + memset(data, 0, data_count * sizeof(u32));
> }
>
> static const struct ethtool_ops lan78xx_ethtool_ops = {
next prev parent reply other threads:[~2024-12-16 13:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 12:09 [PATCH net-next v1 0/6] lan78xx: Preparations for PHYlink Oleksij Rempel
2024-12-16 12:09 ` [PATCH net-next v1 1/6] net: usb: lan78xx: Add error handling to lan78xx_get_regs Oleksij Rempel
2024-12-16 13:07 ` Mateusz Polchlopek [this message]
2024-12-16 13:19 ` Oleksij Rempel
2024-12-16 13:35 ` Mateusz Polchlopek
2024-12-16 12:09 ` [PATCH net-next v1 2/6] net: usb: lan78xx: Use ETIMEDOUT instead of ETIME in lan78xx_stop_hw Oleksij Rempel
2024-12-16 13:08 ` Mateusz Polchlopek
2024-12-16 12:09 ` [PATCH net-next v1 3/6] net: usb: lan78xx: Use action-specific label in lan78xx_mac_reset Oleksij Rempel
2024-12-16 13:13 ` Mateusz Polchlopek
2024-12-16 12:09 ` [PATCH net-next v1 4/6] net: usb: lan78xx: rename phy_mutex to mdiobus_mutex Oleksij Rempel
2024-12-16 12:09 ` [PATCH net-next v1 5/6] net: usb: lan78xx: remove PHY register access from ethtool get_regs Oleksij Rempel
2024-12-16 12:09 ` [PATCH net-next v1 6/6] net: usb: lan78xx: Improve error handling in WoL operations Oleksij Rempel
2024-12-18 4:10 ` [PATCH net-next v1 0/6] lan78xx: Preparations for PHYlink 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=c7ddac7d-debc-44eb-9c43-7746ad3edb55@intel.com \
--to=mateusz.polchlopek@intel.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=phil@raspberrypi.org \
--cc=woojung.huh@microchip.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