netdev - Re: [PATCH net-next v2 1/3] selftests: nic_basic_tests: Add selftest file for basic tests of NIC

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: <55037ff4-aa06-4cd4-bbc1-b1e714fa1fd4@lunn.ch>
Date: Thu, 19 Sep 2024 16:51:18 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Mohan.Prasad@...rochip.com
Cc: netdev@...r.kernel.org, davem@...emloft.net, kuba@...nel.org,
	edumazet@...gle.com, pabeni@...hat.com, shuah@...nel.org,
	linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org,
	horms@...nel.org, brett.creeley@....com, rosenp@...il.com,
	UNGLinuxDriver@...rochip.com, willemb@...gle.com
Subject: Re: [PATCH net-next v2 1/3] selftests: nic_basic_tests: Add selftest
 file for basic tests of NIC

On Thu, Sep 19, 2024 at 10:44:11AM +0000, Mohan.Prasad@...rochip.com wrote:
> Hello Andrew,
> 
> Thank you for the suggestion.
> 
> > EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> > content is safe
> > 
> > > > Since you have batteries included python:
> > > >
> > > > ethtool --json enp2s0
> > > > [sudo] password for andrew:
> > > > [ {
> > > >         "ifname": "enp2s0",
> > > >         "supported-ports": [ "TP","MII" ],
> > > >         "supported-link-modes": [
> > > > "10baseT/Half","10baseT/Full","100baseT/Half","100baseT/Full","1000b
> > > > aseT/
> > > > Full" ],
> > > >         "supported-pause-frame-use": "Symmetric Receive-only",
> > > >         "supports-auto-negotiation": true,
> > > >         "supported-fec-modes": [ ],
> > > >         "advertised-link-modes": [
> > > > "10baseT/Half","10baseT/Full","100baseT/Half","100baseT/Full","1000b
> > > > aseT/
> > > > Full" ],
> > > >         "advertised-pause-frame-use": "Symmetric Receive-only",
> > > >         "advertised-auto-negotiation": true,
> > > >         "advertised-fec-modes": [ ],
> > > >         "auto-negotiation": false,
> > > >         "master-slave-cfg": "preferred slave",
> > > >         "master-slave-status": "unknown",
> > > >         "port": "Twisted Pair",
> > > >         "phyad": 0,
> > > >         "transceiver": "external",
> > > >         "supports-wake-on": "pumbg",
> > > >         "wake-on": "d",
> > > >         "link-detected": false
> > > >     } ]
> > > >
> > > > You can use a json library to do all the parsing for you.
> > >
> > > I tried running the --json option with the ethtool ("ethtool --json enp9s0"),
> > however I am not getting the above output.
> > > Instead it always throws "ethtool: bad command line argument(s)"
> > > I am figuring out what might be missing (or any suggestions would be
> > helpful).
> > 
> > Are you using real ethtool, or busybox? What version of ethtool? I'm using
> > 6.10, but it looks like JSON support was added somewhere around 5.10.
> 
> I have been using ethtool 6.7, updating to ethtool 6.10 solved the problem.

It would be good to gracefully handle this. Have the test fail with a
human readable error indicating ethtool is too old, rather than just
throwing an exception etc.

Digging through the git history, it seems like 6.10 was actually the
first version that supported this:

commit bd1341cd2146bfb89e1239546299102339acbf4d
Author: Fabian Pfitzner <f.pfitzner@...gutronix.de>
Date:   Fri Jul 19 10:55:44 2024 +0200

    add json support for base command
    
    Most subcommands already implement json support for their output. The
    base command (without supplying any subcommand) still lacks this
    option. This patch implments the needed changes to get json output,
    which is printed via "ethtool --json [iface]"
    
    The following design decision were made during implementation:
    - json values like Yes/No are printed as true/false
    - values that are "Unknown" are not printed at all
    - all other json values are not changed
    - keys are printed in lowercase with dashes in between
    
    Signed-off-by: Fabian Pfitzner <f.pfitzner@...gutronix.de>

	Andrew