From: Alexander Duyck <alexander.h.duyck@intel.com>
To: Joe Perches <joe@perches.com>,
Krzysztof Majzerowicz-Jaszcz <cristos@vipserv.org>
Cc: jeffrey.t.kirsher@intel.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers: net: ethernet: intel: e1000: e1000_ethtool.c coding style fixes
Date: Mon, 18 Aug 2014 08:29:48 -0700 [thread overview]
Message-ID: <53F21BEC.2070204@intel.com> (raw)
In-Reply-To: <1408214489.2683.87.camel@joe-AO725>
On 08/16/2014 11:41 AM, Joe Perches wrote:
> On Sat, 2014-08-16 at 11:12 +0200, Krzysztof Majzerowicz-Jaszcz wrote:
>> @@ -1835,11 +1830,11 @@ static void e1000_get_ethtool_stats(struct net_device *netdev,
>> for (i = 0; i < E1000_GLOBAL_STATS_LEN; i++) {
>> switch (e1000_gstrings_stats[i].type) {
>> case NETDEV_STATS:
>> - p = (char *) netdev +
>> + p = (char *)netdev +
>> e1000_gstrings_stats[i].stat_offset;
>> break;
>> case E1000_STATS:
>> - p = (char *) adapter +
>> + p = (char *)adapter +
>> e1000_gstrings_stats[i].stat_offset;
>> brseak;
>> }
>
> Maybe use a temporary for &e1000_gstring_stats[i]
>
> Something like: (w/ void * for char *, WARN_ONCE, trigraph->if/else)
>
> static void e1000_get_ethtool_stats(struct net_device *netdev,
> struct ethtool_stats *stats, u64 *data)
> {
> struct e1000_adapter *adapter = netdev_priv(netdev);
> int i;
> void *p = NULL;
> const struct e1000_stats *stat = e1000_gstring_stats;
>
> e1000_update_stats(adapter);
>
> for (i = 0; i < E1000_GLOBAL_STATS_LEN; i++) {
> switch (stat->type) {
> case NETDEV_STATS:
> p = (void *)netdev + stat->stat_offset;
> break;
> case E1000_STATS:
> p = (void *)adapter + stat->stat_offset;
> break;
> default:
> WARN_ONCE(1, "Invalid E1000 stat type: %u index %d\n",
> stat->type, i);
> break;
> }
>
> if (stat->sizeof_stat == sizeof(u64))
> data[i] = *(u64 *)p;
> else
> data[i] = *(u32 *)p;
>
> stat++;
> }
> }
>
Doing any kind of pointer math on a void pointer is generally unsafe as
it is an incomplete type. The only reason why it works in GCC is
because GCC has a nonstandard extension that makes it report as having a
size of 1.
This is why the math is being done on a char * as it is a complete type
with a size of 1.
Thanks,
Alex
next prev parent reply other threads:[~2014-08-18 15:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-16 9:12 [PATCH] drivers: net: ethernet: intel: e1000: e1000_ethtool.c coding style fixes Krzysztof Majzerowicz-Jaszcz
2014-08-16 18:41 ` Joe Perches
2014-08-18 15:29 ` Alexander Duyck [this message]
2014-08-18 15:31 ` Joe Perches
2014-08-18 15:36 ` Krzysztof Majzerowicz-Jaszcz
2014-08-18 15:40 ` Joe Perches
2014-08-18 15:43 ` Krzysztof Majzerowicz-Jaszcz
2014-08-18 15:45 ` Alexander Duyck
2014-08-18 16:29 ` Joe Perches
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53F21BEC.2070204@intel.com \
--to=alexander.h.duyck@intel.com \
--cc=cristos@vipserv.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).