netdev - Re: Question on ethtool strategy wrt legacy ioctl

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

Message-ID: <4c6221c6-6c14-4799-8cc6-0f8129a8dcab@lunn.ch>
Date: Fri, 16 Feb 2024 18:08:57 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Heiner Kallweit <hkallweit1@...il.com>
Cc: Michal Kubecek <mkubecek@...e.cz>, Jakub Kicinski <kuba@...nel.org>,
	Paolo Abeni <pabeni@...hat.com>, David Miller <davem@...emloft.net>,
	Eric Dumazet <edumazet@...gle.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	Russell King - ARM Linux <linux@...linux.org.uk>
Subject: Re: Question on ethtool strategy wrt legacy ioctl

On Fri, Feb 16, 2024 at 11:53:26AM +0100, Heiner Kallweit wrote:
> When working on ethtool functionality on both sides, userspace and kernel, the following questions came to my mind:
> 
> - Is there any good reason why somebody would set CONFIG_ETHTOOL_NETLINK = n ?

An embedded kernel might do this, to slim the kernel down a
bit. busybox does not have an implementation of ethtool(1), but it
does make a couple of ethtool ioctl calls in some of its commands.

> - If for a certain ethtool functionality ioctl and netlink is
>   supported, can the ioctl part be removed more sooner than later?

Depending on what you removed, that would break busybox. We cannot
force users to make use of netlink.

      Andrew