[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YFyAl36ShF8mZbM8@lunn.ch>
Date: Thu, 25 Mar 2021 13:22:47 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Jakub Kicinski <kuba@...nel.org>
Cc: davem@...emloft.net, netdev@...r.kernel.org,
ecree.xilinx@...il.com, michael.chan@...adcom.com,
damian.dybek@...el.com, paul.greenwalt@...el.com,
rajur@...lsio.com, jaroslawx.gawin@...el.com, vkochan@...vell.com,
alobakin@...me, snelson@...sando.io, shayagr@...zon.com,
ayal@...dia.com, shenjian15@...wei.com, saeedm@...dia.com,
mkubecek@...e.cz, roopa@...dia.com
Subject: Re: [PATCH net-next 3/6] ethtool: fec: sanitize
ethtool_fecparam->reserved
On Wed, Mar 24, 2021 at 06:11:57PM -0700, Jakub Kicinski wrote:
> struct ethtool_fecparam::reserved is never looked at by the core.
> Make sure it's actually 0. Unfortunately we can't return an error
> because old ethtool doesn't zero-initialize the structure for SET.
Hi Jakub
What makes it totally useless for future uses with SET. So the
documentation should probably be something like:
* @reserved: Reserved for future GET extensions.
*
* Older ethtool(1) leave @reserved uninitialised when calling SET or
* GET. Hence it can only be used to return a value to userspace with
* GET. Currently the value returned is guaranteed to be zero.
The rest looks O.K.
Andrew
Powered by blists - more mailing lists