From: Andreas Henriksson <andreas@fatal.se>
To: netdev@vger.kernel.org
Cc: 199054@bugs.debian.org
Subject: Bug#199054: iproute2 showing wrong number of bytes on 64bit architectures.
Date: Tue, 10 Jul 2007 13:58:51 +0200 [thread overview]
Message-ID: <20070710115851.GA21929@scream.fatal.se> (raw)
Hello!
While investigating the problems reported in Debian bug #199054
(http://bugs.debian.org/199054), stating that the RX/TX bytes differ between
ifconfig and ip(route2) I came across this:
include/linux/if_link.h (used in kernel and iproute2 source):
/* The struct should be in sync with struct net_device_stats */
struct rtnl_link_stats
{
__u32 ...;
__u32 ...;
__u32 ...;
__u32 ...;
...
include/linux/netdevice.h:
struct net_device_stats
{
unsigned long ...;
unsigned long ...;
unsigned long ...;
unsigned long ...;
unsigned long ...;
....
This will be a problem when unsigned long isn't 32bits, but I guess the
rtnetlink message size is static for good reason.
Can someone please advise on how to fix this?
--
Regards,
Andreas Henriksson
reply other threads:[~2007-07-10 11:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070710115851.GA21929@scream.fatal.se \
--to=andreas@fatal.se \
--cc=199054@bugs.debian.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).