netdev - Re: [RFC net-next 0/5] devlink: Add unique identifier to devlink port function

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250425105145.6095c111@kernel.org>
Date: Fri, 25 Apr 2025 10:51:45 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Jiri Pirko <jiri@...nulli.us>
Cc: Moshe Shemesh <moshe@...dia.com>, netdev@...r.kernel.org, "David S.
 Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo
 Abeni <pabeni@...hat.com>, Simon Horman <horms@...nel.org>, Donald Hunter
 <donald.hunter@...il.com>, Jonathan Corbet <corbet@....net>, Andrew Lunn
 <andrew+netdev@...n.ch>, Tariq Toukan <tariqt@...dia.com>, Saeed Mahameed
 <saeedm@...dia.com>, Mark Bloch <mbloch@...dia.com>
Subject: Re: [RFC net-next 0/5] devlink: Add unique identifier to devlink
 port function

On Fri, 25 Apr 2025 13:26:01 +0200 Jiri Pirko wrote:
>> Makes sense, tho, could you please use UUID?
>> Let's use industry standards when possible, not "arbitrary strings".  
> 
> Well, you could make the same request for serial number of asic and board.
> Could be uuids too, but they aren't. I mean, it makes sense to have all
> uids as uuid, but since the fw already exposes couple of uids as
> arbitrary strings, why this one should be treated differently all of the
> sudden?

Are you asking me what the difference is here, or you're just telling
me that I'm wrong and inconsistent?