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
| ||
|
Message-Id: <20170504013651.GA26492@gwshan> Date: Thu, 4 May 2017 11:36:51 +1000 From: Gavin Shan <gwshan@...ux.vnet.ibm.com> To: Andrew Lunn <andrew@...n.ch> Cc: Gavin Shan <gwshan@...ux.vnet.ibm.com>, netdev@...r.kernel.org, joe@...ches.com, kubakici@...pl, f.fainelli@...il.com, davem@...emloft.net Subject: Re: [PATCH v4 net-next 04/10] net/ncsi: Ethtool operation to get NCSI topology On Thu, May 04, 2017 at 02:49:33AM +0200, Andrew Lunn wrote: >> +void ncsi_ethtool_register_dev(struct net_device *dev) >> +{ >> + struct ethtool_ops *ops; >> + >> + ops = (struct ethtool_ops *)(dev->ethtool_ops); > >Why do you need the cast here? > >Ah, is it because net_device has: > > const struct ethtool_ops *ethtool_ops; > >i.e. you are casting off the const. > >> + if (!ops) >> + return; >> + >> + ops->get_ncsi_channels = ncsi_get_channels; > >and here you modify it. Which is going to blow up, because it will be >in a read only segment and should throw an opps when you write to it? > >You need to export ncsi_get_channels, and let the underlying driver >add it to its own ethtool_ops. > I didn't see oops because of this on the ARM board where I did the testing. The intention was to make ethtool invisible to drivers, for simplicity. However, we need to expose ethtool to driver when the HW and SW statistics are conveyed by ETHTOOL_GSTATS as agree'd in another thread. Cheers, Gavin
Powered by blists - more mailing lists