netdev - Re: [PATCH] net: phy: adin1100: Fix nullptr exception for phy interrupts

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <322d5543-4d13-48a7-af58-daa8cc840f05@lunn.ch>
Date: Thu, 18 Jan 2024 17:53:58 +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: [PATCH] net: phy: adin1100: Fix nullptr exception for phy
 interrupts

On Thu, Jan 18, 2024 at 11:43:41AM +0100, Andre Werner wrote:
> If using ADIN1100 as an external phy, e.g. in combination with
> "smsc95xx", we ran into nullptr exception by creating a link.
> 
> In our case the "smsc95xx" does not check for an available interrupt handler
> on external phy driver to use poll instead of interrupts if no handler is
> available. So we decide to implement a small handler in the phy driver
> to support other MACs as well.
> 
> I update the driver to add an interrupt handler because libphy
> does not check if their is a interrupt handler available either.
> 
> There are several interrupts maskable at the phy, but only link change interrupts
> are handled by the driver yet.
> 
> We tested the combination "smsc95xx" and "adin1100" with Linux Kernel 6.6.9
> and Linux Kernel 6.1.0, respectively.

Hi Andre

A few different things....

Please could you give more details of the null pointer
exception. phylib should test if the needed methods have been
implemented in the PHY driver, and not tried to use interrupts when
they are missing. It should of polled the PHY. So i would like to
understand what went wrong. Maybe we have a phylib core bug we should
be fixing. Or a bug in the smsc95xx driver.

Please take a read of
https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html

Patches like this should be against net-next, not 6.6.9 etc. Also,
net-next is currently closed due to the merge window being open. Its
fine to post patches, but please mark them RFC until the merge window
is over.

The patch itself looks O.K, but i would make the commit message more
formal. You can add additional comments under the --- which will not
become part of the git history.

       Andrew