From: Stephen Hemminger <stephen@networkplumber.org>
To: Stephen Gallagher <sgallagh@redhat.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] iproute2: fix type incompatibility in ifstat.c
Date: Tue, 6 Feb 2024 19:12:09 -0800 [thread overview]
Message-ID: <20240206191209.3aaf9916@hermes.local> (raw)
In-Reply-To: <20240206142213.777317-1-sgallagh@redhat.com>
On Tue, 6 Feb 2024 09:22:06 -0500
Stephen Gallagher <sgallagh@redhat.com> wrote:
> Throughout ifstat.c, ifstat_ent.val is accessed as a long long unsigned
> type, however it is defined as __u64. This works by coincidence on many
> systems, however on ppc64le, __u64 is a long unsigned.
>
> This patch makes the type definition consistent with all of the places
> where it is accessed.
>
> Signed-off-by: Stephen Gallagher <sgallagh@redhat.com>
> ---
Why not fix the use of unsigned long long to be __u64 instead?
That would make more sense.
Looking at ifstat it has other problems.
It doesn't check the sizes in the netlink response.
It really should be using 64 bit stat counters, not the legacy 32 bit
values. (ie IFLA_STATS64). Anyone want to take this on?X
Also, the cpu_hits offload code is a wart. If it is of interest, it should
be more than one stat.
One last issue, is that change the size of this structure will break old
history files.
next prev parent reply other threads:[~2024-02-07 3:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 14:22 [PATCH] iproute2: fix type incompatibility in ifstat.c Stephen Gallagher
2024-02-06 16:17 ` Andrea Claudi
2024-02-06 16:52 ` [PATCH iproute] Fix " Stephen Gallagher
2024-02-06 16:52 ` [PATCH] iproute2: fix " Stephen Gallagher
2024-02-15 3:10 ` patchwork-bot+netdevbpf
2024-02-07 3:12 ` Stephen Hemminger [this message]
2024-02-07 6:44 ` Florian Weimer
2024-02-08 18:17 ` Stephen Gallagher
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=20240206191209.3aaf9916@hermes.local \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=sgallagh@redhat.com \
/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).