netdev - Re: [PATCH v2] net: phy: Have __phy

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: <20180115.125013.1494098943775766238.davem@davemloft.net>
Date:   Mon, 15 Jan 2018 12:50:13 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     andrew@...n.ch
Cc:     geert@...ux-m68k.org, niklas.cassel@...s.com,
        rmk+kernel@....linux.org.uk, f.fainelli@...il.com,
        netdev@...r.kernel.org
Subject: Re: [PATCH v2] net: phy: Have __phy_modify return 0 on success

From: Andrew Lunn <andrew@...n.ch>
Date: Fri, 12 Jan 2018 15:01:36 +0100

> __phy_modify would return the old value of the register before it was
> modified. Thus on success, it does not return 0, but a positive value.
> Thus functions using phy_modify, which is a wrapper around
> __phy_modify, can start returning > 0 on success, rather than 0. As a
> result, breakage has been noticed in various places, where 0 was
> assumed.
> 
> Code inspection does not find any current location where the return of
> the old value is currently used. So have __phy_modify return 0 on
> success. When there is a real need for the old value, either a new
> accessor can be added, or an additional parameter passed.
> 
> Fixes: fea23fb591cc ("net: phy: convert read-modify-write to phy_modify()")
> Fixes: 2b74e5be17d2 ("net: phy: add phy_modify() accessor")
> Reported-by: Geert Uytterhoeven <geert@...ux-m68k.org>
> Tested-by: Geert Uytterhoeven <geert+renesas@...der.be>
> Signed-off-by: Andrew Lunn <andrew@...n.ch>
> ---
> v2: space before :
>     additional fixes tag
>     Tested-by

Applied to net-next, thanks Andrew.