netdev - Re: [RFC net-next v3 1/2] net: phy: phy_device Prevent nullptr exceptions on ISR

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <fa47c497-a831-4e11-bbb9-c3901b174d0d@lunn.ch>
Date: Fri, 19 Jan 2024 14:27:01 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Andre Werner <andre.werner@...tec-electronic.com>
Cc: hkallweit1@...il.com, davem@...emloft.net, edumazet@...gle.com,
	kuba@...nel.org, pabeni@...hat.com, linux@...linux.org.uk,
	netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC net-next v3 1/2] net: phy: phy_device Prevent nullptr
 exceptions on ISR

On Fri, Jan 19, 2024 at 10:32:25AM +0100, Andre Werner wrote:
> If phydev->irq is set unconditionally by MAC drivers, check
> for valid interrupt handler or fall back to polling mode to prevent
> nullptr exceptions.

Hi Andre

A few more process things...

Please don't post a new version within 24 hours. Reviews need time to
review, and you could miss comments made on older versions of the
patches.

For a multi part patch set, its normal to include a clover
letter. When using git format-patch add --cover-letter and than edit
patch 0000-*.patch to describe the big picture of what the patchset
does. The text will be used for the merge commit message.
 
> Signed-off-by: Andre Werner <andre.werner@...tec-electronic.com>
> ---
> v3:
> - No changes to v2. Just to complete the series.
> ---
>  drivers/net/phy/phy_device.c | 22 +++++++++++++++++-----
>  1 file changed, 17 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/net/phy/phy_device.c b/drivers/net/phy/phy_device.c
> index 3611ea64875e..3986e103d25e 100644
> --- a/drivers/net/phy/phy_device.c
> +++ b/drivers/net/phy/phy_device.c
> @@ -1413,6 +1413,11 @@ int phy_sfp_probe(struct phy_device *phydev,
>  }
>  EXPORT_SYMBOL(phy_sfp_probe);
>  
> +static bool phy_drv_supports_irq(struct phy_driver *phydrv)
> +{
> +	return phydrv->config_intr && phydrv->handle_interrupt;
> +}
> +
>  /**
>   * phy_attach_direct - attach a network device to a given PHY device pointer
>   * @dev: network device to attach
> @@ -1527,6 +1532,18 @@ int phy_attach_direct(struct net_device *dev, struct phy_device *phydev,
>  	if (phydev->dev_flags & PHY_F_NO_IRQ)
>  		phydev->irq = PHY_POLL;
>  
> +	/*
> +	 * Some drivers may add IRQ numbers unconditionally to a phy device that does
> +	 * not implement an interrupt handler after phy_probe is already done.
> +	 * Reset to PHY_POLL to prevent nullptr exceptions in that case.
> +	 */
> +	if (!phy_drv_supports_irq(phydev->drv) && phy_interrupt_is_valid(phydev)) {
> +		phydev_warn(phydev,
> +			    "No handler for IRQ=%d available. Falling back to polling mode\n",
> +			    phydev->irq);
> +		phydev->irq = PHY_POLL;
> +	}

Please drop the phydev_warn(). Interrupt handling has always been
optional, and we have always silently dropped back to polling if
interrupts are not supported.

The comment wording is also not great. The MAC driver is not supposed
to have any idea what the PHY driver is. It just uses the phylib API,
which is PHY driver independent. So the MAC driver cannot tell if the
PHY driver supports interrupts or not.

I don't think a comment is needed. The code is pretty readable as is.

    Andrew

---
pw-bot: cr