netdev - Re: PHY firmware update method

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: <20230131104122.20c143a2@kernel.org>
Date:   Tue, 31 Jan 2023 10:41:22 -0800
From:   Jakub Kicinski <kuba@...nel.org>
To:     "Russell King (Oracle)" <linux@...linux.org.uk>
Cc:     Michael Walle <michael@...le.cc>, Andrew Lunn <andrew@...n.ch>,
        Jiri Pirko <jiri@...nulli.us>,
        Heiner Kallweit <hkallweit1@...il.com>, netdev@...r.kernel.org,
        Keller Jacob E <jacob.e.keller@...el.com>
Subject: Re: PHY firmware update method

On Tue, 31 Jan 2023 16:29:04 +0000 Russell King (Oracle) wrote:
> I really don't like the idea of the kernel automatically updating
> non-volatile firmware - that sounds to me like a recipe for all
> sorts of disasters.

FWIW we had a concept of "FW load policy" in devlink but IDK if it
addresses the concern sufficiently. For mlxsw IIRC the load policy
"from disk" means "flash the device if loaded FW is older".