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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sun, 4 Oct 2020 12:46:31 +0000 From: David Laight <David.Laight@...LAB.COM> To: 'Ido Schimmel' <idosch@...sch.org>, "netdev@...r.kernel.org" <netdev@...r.kernel.org> CC: "davem@...emloft.net" <davem@...emloft.net>, "kuba@...nel.org" <kuba@...nel.org>, "mkubecek@...e.cz" <mkubecek@...e.cz>, "f.fainelli@...il.com" <f.fainelli@...il.com>, "andrew@...n.ch" <andrew@...n.ch>, "saeedm@...dia.com" <saeedm@...dia.com>, "ayal@...dia.com" <ayal@...dia.com>, "mlxsw@...dia.com" <mlxsw@...dia.com>, Ido Schimmel <idosch@...dia.com> Subject: RE: [RFC PATCH net-next v2] ethtool: Improve compatibility between netlink and ioctl interfaces From: Ido Schimmel > Sent: 04 October 2020 11:17 > > With the ioctl interface, when autoneg is enabled, but without > specifying speed, duplex or link modes, the advertised link modes are > set to the supported link modes by the ethtool user space utility. ... > Fix this incompatibility problem by introducing a new flag in the > ethtool netlink request header: 'ETHTOOL_FLAG_LEGACY'. The purpose of > the flag is to indicate to the kernel that it needs to be compatible > with the legacy ioctl interface. A patch to the ethtool user space > utility will make sure the flag is always set. You need to do that the other way around. You can't assume the kernel and application are updated at the same time. David - Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK Registration No: 1397386 (Wales)
Powered by blists - more mailing lists