netdev - Re: [patch net-next] net: devlink: expose the info about version representing a component

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]

Date:   Mon, 7 Nov 2022 18:03:06 +0100
From:   Jiri Pirko <jiri@...nulli.us>
To:     Jakub Kicinski <kuba@...nel.org>
Cc:     netdev@...r.kernel.org, davem@...emloft.net, pabeni@...hat.com,
        edumazet@...gle.com
Subject: Re: [patch net-next] net: devlink: expose the info about version
 representing a component

Mon, Nov 07, 2022 at 05:52:18PM CET, kuba@...nel.org wrote:
>On Sat, 5 Nov 2022 10:26:33 +0100 Jiri Pirko wrote:
>>> Didn't I complain that this makes no practical sense because
>>> user needs to know what file to flash, to which component?
>>> Or was that a different flag that I was complaining about?  
>> 
>> Different. That was about exposing a default component.
>
>Oh, my bad. But I think the same justification applies here.
>Overloading the API with information with no clear use seems
>counter-productive to me.

Well, it gives the user hint about what he can pass as a "component
name" on the cmdline. Otherwise, the user has no clue.