netdev - [PATCH ethtool 0/2] module_common: adjust the JSON output for per-lane signals

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-next>] [day] [month] [year] [list]

Message-ID: <20250529142033.2308815-1-kuba@kernel.org>
Date: Thu, 29 May 2025 07:20:31 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: mkubecek@...e.cz
Cc: danieller@...dia.com,
	idosch@...sch.org,
	netdev@...r.kernel.org,
	Jakub Kicinski <kuba@...nel.org>
Subject: [PATCH ethtool 0/2] module_common: adjust the JSON output for per-lane signals

I got some feedback from users trying to integrate the SFP JSON
output to Meta's monitoring systems. The loss / fault signals
are currently a bit awkward to parse. This patch set changes
the format, is it still okay to merge it (as a fix?)
I think it's a worthwhile improvement, not sure how many people
depend on the current JSON format after 1 release..

Jakub Kicinski (2):
  module_common: always print per-lane status in JSON
  module_common: print loss / fault signals as bool

 module-common.c | 10 +++-------
 1 file changed, 3 insertions(+), 7 deletions(-)

-- 
2.49.0