netdev - Re: [PATCH net] net: phy: make phy_error() report which PHY has failed

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: <20191219.141433.159371363914521057.davem@davemloft.net>
Date:   Thu, 19 Dec 2019 14:14:33 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     andrew@...n.ch
Cc:     rmk+kernel@...linux.org.uk, f.fainelli@...il.com,
        hkallweit1@...il.com, netdev@...r.kernel.org
Subject: Re: [PATCH net] net: phy: make phy_error() report which PHY has
 failed

From: Andrew Lunn <andrew@...n.ch>
Date: Thu, 19 Dec 2019 22:05:03 +0100

>> I think I agree with Heiner that it is valuable to know whether the
>> error occurred from the interrupt handler or the state machine (and
>> if the state machine, where that got called from).
>> 
>> So I totally disagree with removing the backtrace, sorry.
> 
> Russell does have a point about the backtrace not giving an indication
> of which phy experienced the error. So adding the phydev_err() call,
> which will prefix the print with an identifier for the PHY, is a good
> idea. So we should add that, and keep the WARN().

Agreed.