linux-kernel - Re: [RFC PATCH 0/9] ethtool netlink interface (WiP)

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: <20171211.120144.1060832843526341781.davem@davemloft.net>
Date:   Mon, 11 Dec 2017 12:01:44 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     jiri@...nulli.us
Cc:     mkubecek@...e.cz, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 0/9] ethtool netlink interface (WiP)

From: Jiri Pirko <jiri@...nulli.us>
Date: Mon, 11 Dec 2017 17:32:46 +0100

> I think that it does not make sense to convert ethtool->netlink_ethtool
> 1:1 feature wise. Now we have devlink, ritch switch representation
> model, tc offload and many others. Lot of things that are in
> ethtool, should be done in devlink. Also, there are couple of things
> that should just die - nice example is ethtool --config-ntuple - we
> should use tc for that.

Whilst I do agree that devlink is probably a good place for this stuff
(we want to be able to do ethetool things on objects that lack a netdev)
I do not agree with the tc angle.

It is entirely appropriate to set the ntuple settings of a driver
without being required to use TC or similar.

All you are going to do with your suggestion is make people keep using
the existing ethtool ioctl, because they'll say "screw this, I'm not
using TC I have something which works just fine already".  And that's
not the goal of putting this stuff into netlink, we want people to
use the new facilities and move off of the ioctl.