netdev - Re: [PATCH v2] net: dsa: realtek: rtl8366rb: Serialize indirect PHY register access

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: <b8e254c50ca23571a640bbc230730ab4219b9308.camel@redhat.com>
Date:   Tue, 10 May 2022 12:45:35 +0200
From:   Paolo Abeni <pabeni@...hat.com>
To:     Linus Walleij <linus.walleij@...aro.org>,
        Andrew Lunn <andrew@...n.ch>,
        Vivien Didelot <vivien.didelot@...il.com>,
        Florian Fainelli <f.fainelli@...il.com>,
        Vladimir Oltean <olteanv@...il.com>,
        "David S . Miller" <davem@...emloft.net>,
        Jakub Kicinski <kuba@...nel.org>
Cc:     netdev@...r.kernel.org,
        Alvin Šipraga <alsi@...g-olufsen.dk>,
        kernel test robot <lkp@...el.com>
Subject: Re: [PATCH v2] net: dsa: realtek: rtl8366rb: Serialize indirect PHY
 register access

Hello,

On Mon, 2022-05-09 at 01:03 +0200, Linus Walleij wrote:
> From: Alvin Šipraga <alsi@...g-olufsen.dk>
> 
> Lock the regmap during the whole PHY register access routines in
> rtl8366rb.
> 
> Signed-off-by: Alvin Šipraga <alsi@...g-olufsen.dk>
> Reported-by: kernel test robot <lkp@...el.com>
> Tested-by: Linus Walleij <linus.walleij@...aro.org>
> Signed-off-by: Linus Walleij <linus.walleij@...aro.org>
> ---
> ChangeLog v1->v2:
> - Make sure to always return a properly assigned error
>   code on the error path in rtl8366rb_phy_read()
>   found by the kernel test robot.
> 
> I have tested that this does not create any regressions,
> it makes more sense to have this applied than not. First
> it is related to the same family as the other ASICs, also
> it makes perfect logical sense to enforce serialization
> of these reads/writes.

I'm unable to understand if this is targeting the 'net' or the 'net-
next' tree, could you please clarify?

If targeting 'net', adding an additional, suitable 'Fixes' tag would be
nice.

Thanks!

Paolo