[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c37ee9e7-53de-4c21-b0cb-4cfb0936bc1e@lunn.ch>
Date: Wed, 20 Aug 2025 22:42:47 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Dong Yibo <dong100@...se.com>
Cc: andrew+netdev@...n.ch, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, horms@...nel.org,
corbet@....net, gur.stavi@...wei.com, maddy@...ux.ibm.com,
mpe@...erman.id.au, danishanwar@...com, lee@...ger.us,
gongfan1@...wei.com, lorenzo@...nel.org, geert+renesas@...der.be,
Parthiban.Veerasooran@...rochip.com, lukas.bulwahn@...hat.com,
alexanderduyck@...com, richardcochran@...il.com,
netdev@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 5/5] net: rnpgbe: Add register_netdev
> +static int rnpgbe_get_permanent_mac(struct mucse_hw *hw,
> + u8 *mac_addr)
> +{
> + struct device *dev = &hw->pdev->dev;
> +
> + if (mucse_fw_get_macaddr(hw, hw->pfvfnum, mac_addr, hw->port) ||
> + !is_valid_ether_addr(mac_addr)) {
> + dev_err(dev, "Failed to get valid MAC from FW\n");
> + return -EINVAL;
I _think_ mucse_fw_get_macaddr() can return -EINTR, because deep down,
it has a call to mutex_lock_interruptible(). If that happens, you
should not return iEINVAL, it is not an invalid value, its just an
interrupted system call.
This is what i'm talking about needing careful review...
Andrew
---
pw-bot: cr
Powered by blists - more mailing lists