From: Jakub Kicinski <kuba@kernel.org>
To: Rand Deeb <rand.sec96@gmail.com>
Cc: Denis Kirjanov <kirjanov@gmail.com>,
Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Andrew Lunn <andrew+netdev@lunn.ch>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
deeb.rand@confident.ru, lvc-project@linuxtesting.org,
shda@confident.ru
Subject: Re: [PATCH net] net: sundance: fix sign extension of the octet counters
Date: Tue, 20 Oct 2026 18:11:22 -0700 [thread overview]
Message-ID: <20261020181122.53fd0c79@kernel.org> (raw)
In-Reply-To: <20261020234434.318-1-rand.sec96@gmail.com>
On Wed, 21 Oct 2026 02:44:34 +0300 Rand Deeb wrote:
> get_stats() adds the upper halves of the 32-bit TxOctets and RxOctets
> hardware counters to the byte statistics with
>
> dev->stats.tx_bytes += ioread16(ioaddr + TxOctetsHigh) << 16;
>
> On architectures that use the ioread16() from asm-generic/io.h, which
> returns u16, the value is promoted to int before the shift. When the
> high word is 0x8000 or more, the result does not fit in a positive int
> and ends up negative, and adding it to the unsigned long counter
> sign-extends it. On 64-bit kernels tx_bytes and rx_bytes then end up
> 2^32 lower than they should be. x86 and m68k are not affected, because
> their ioread16() comes from asm-generic/iomap.h and returns unsigned int.
>
> Cast the high word to u32 before shifting, so the result is the same on
> all architectures.
We don't take LLM slop fixes for ancient hw
--
pw-bot: reject
next prev parent reply other threads:[~2026-10-21 1:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 23:44 [PATCH net] net: sundance: fix sign extension of the octet counters Rand Deeb
2026-10-20 23:49 ` netdev-bot+sinfo
2026-10-21 1:11 ` Jakub Kicinski [this message]
2026-10-21 2:25 ` Rand Deeb
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=20261020181122.53fd0c79@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=deeb.rand@confident.ru \
--cc=edumazet@kernel.org \
--cc=kirjanov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rand.sec96@gmail.com \
--cc=shda@confident.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.