netdev - Re: [PATCH ethtool-next 08/14] cmis: Enable JSON output support in CMIS modules

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: <20250130082435.0a3a7922@kernel.org>
Date: Thu, 30 Jan 2025 08:24:35 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Danielle Ratson <danieller@...dia.com>
Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "mkubecek@...e.cz"
 <mkubecek@...e.cz>, "matt@...verse.com.au" <matt@...verse.com.au>,
 "daniel.zahka@...il.com" <daniel.zahka@...il.com>, Amit Cohen
 <amcohen@...dia.com>, NBU-mlxsw <NBU-mlxsw@...hange.nvidia.com>
Subject: Re: [PATCH ethtool-next 08/14] cmis: Enable JSON output support in
 CMIS modules

On Thu, 30 Jan 2025 12:38:56 +0000 Danielle Ratson wrote:
> > > Yes, the unit is implied by the key is hardcoded. Same as for the
> > > regular output, it should give the costumer idea about the scale.
> > > There are also temperature fields that could be either F or C degrees.
> > > So overall , the units fields should align all the fields that implies
> > > some sort of scale.  
> > 
> > Some sort of a schema would be a better place to document the unit of the
> > fields, IMO.  
> 
> So should the units fields be removed entirely?  And only be
> documented in the json schema file?

Yes, more than happy to hear from others but a schema file would
be my first choice. Short of that as long as the unit is the same
as in the plain text output there should also not be any ambiguity.