From: David Laight <david.laight.linux@gmail.com>
To: David Yang <mmyangfl@gmail.com>
Cc: netdev@vger.kernel.org, Dan Carpenter <dan.carpenter@linaro.org>,
Andrew Lunn <andrew@lunn.ch>, Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: dsa: yt921x: Fix missing type casting to u64
Date: Fri, 24 Oct 2025 13:21:17 +0100 [thread overview]
Message-ID: <20251024132117.43f39504@pumpkin> (raw)
In-Reply-To: <20251024084918.1353031-1-mmyangfl@gmail.com>
On Fri, 24 Oct 2025 16:49:13 +0800
David Yang <mmyangfl@gmail.com> wrote:
> Reported by the following Smatch static checker warning:
>
> drivers/net/dsa/yt921x.c:702 yt921x_read_mib()
> warn: was expecting a 64 bit value instead of '(~0)'
>
> Reported-by: Dan Carpenter <dan.carpenter@linaro.org>
> Closes: https://lore.kernel.org/netdev/aPsjYKQMzpY0nSXm@stanley.mountain/
> Signed-off-by: David Yang <mmyangfl@gmail.com>
> ---
> drivers/net/dsa/yt921x.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/dsa/yt921x.c b/drivers/net/dsa/yt921x.c
> index ab762ffc4661..8baed8107512 100644
> --- a/drivers/net/dsa/yt921x.c
> +++ b/drivers/net/dsa/yt921x.c
> @@ -699,7 +699,7 @@ static int yt921x_read_mib(struct yt921x_priv *priv, int port)
> if (val < (u32)val)
That check is wrong as well, probably (val0 < (u32)val) is right.
But the code is confusing.
> /* overflow */
> val += (u64)U32_MAX + 1;
> - val &= ~U32_MAX;
> + val &= ~(u64)U32_MAX;
> val |= val0;
How about:
if (desc->size <= 1) {
u64 old_val = *valp;
val = upper32_bits(old_val) | val0;
if (val < old_val)
val += 1ull << 32;
}
There is also an inconsistency with the read of *valp and the
WRITE_ONCE() lower down.
If there is a READ_ONCE() elsewhere then it not going to work on
32bit architectures - since both the read and write are still
likely to be two memory cycles.
David
> } else {
> res = yt921x_reg_read(priv, reg + 4, &val1);
prev parent reply other threads:[~2025-10-24 12:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 8:49 [PATCH net-next] net: dsa: yt921x: Fix missing type casting to u64 David Yang
2025-10-24 12:21 ` David Laight [this message]
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=20251024132117.43f39504@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=andrew@lunn.ch \
--cc=dan.carpenter@linaro.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmyangfl@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@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