[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210325090233.3128075f@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Thu, 25 Mar 2021 09:02:33 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Andrew Lunn <andrew@...n.ch>
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 Thu, 25 Mar 2021 13:22:47 +0100 Andrew Lunn wrote:
> 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.
I didn't spell this out because we'll move to netlink as next
step so the ioctl structure is less relevant, but will do!
Powered by blists - more mailing lists