From: Yury Norov <yury.norov@gmail.com>
To: Yazen Ghannam <yazen.ghannam@amd.com>
Cc: Rasmus Villemoes <linux@rasmusvillemoes.dk>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] linux/bits.h: Squash unsigned comparison warning for GENMASK
Date: Tue, 4 Feb 2025 16:26:20 -0500 [thread overview]
Message-ID: <Z6KF8UBsQ4NmR9KS@thinkpad> (raw)
In-Reply-To: <20250204-fix-genmask-warn-v1-1-626de7a30090@amd.com>
On Tue, Feb 04, 2025 at 05:13:16PM +0000, Yazen Ghannam wrote:
> Cast inputs to 'long' to avoid the following 'type-limits' warning:
> warning: comparison of unsigned expression in ‘< 0’ is always false
>
> The 'long' type can hold +/- 2G which far exceeds valid inputs for the
> GENMASK helpers (current max use is 128 bits).
>
> Idea is similar to implementation in __is_nonneg().
>
> Signed-off-by: Yazen Ghannam <yazen.ghannam@amd.com>
> ---
> Note to maintainers:
> I found some previous discussions on this topic in the mailing list
> archives. The upstream code has changed a bit since then, and this
> proposed solution seems fairly simple when based on the latest code.
>
> I figured I'd look at something outside my normal focus areas. I
> apologize for the noise if this solution is too naive or incomplete.
>
> Thanks!
Hi Yazen,
Wtype-limits is enabled in W=2 only, see scripts/Makefile.extrawarn.
We normally shouldn't see this type of warnings even when compiling
with W=1, at all.
We have quite a lot callers in kernel already that do GENMASK(xxx, 0)
yury:linux$ git grep GENMASK | grep 0\) | wc -l
13788
And nobody complained so far.
Still, I tried to compile a small userspace app that calls
__GENMASK(10,0), and found no warnings with Wall, Wextra and
Wtype-limits enabled.
Can you share more about your compiler, compilation command and config?
> ---
> include/linux/bits.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/bits.h b/include/linux/bits.h
> index 61a75d3f294b..318346f2a5a6 100644
> --- a/include/linux/bits.h
> +++ b/include/linux/bits.h
> @@ -21,7 +21,7 @@
> #if !defined(__ASSEMBLY__)
> #include <linux/build_bug.h>
> #include <linux/compiler.h>
> -#define GENMASK_INPUT_CHECK(h, l) BUILD_BUG_ON_ZERO(const_true((l) > (h)))
> +#define GENMASK_INPUT_CHECK(h, l) BUILD_BUG_ON_ZERO(const_true((long)(l) > (long)(h)))
This implies that GENMASK() is OK with signed input, so negative too.
It's not true. For me typecasting to a signed type just to shut the
compiler is a bad idea
Thanks,
Yury
> #else
> /*
> * BUILD_BUG_ON_ZERO is not available in h files included from asm files,
>
> ---
> base-commit: 0de63bb7d91975e73338300a57c54b93d3cc151c
> change-id: 20250204-fix-genmask-warn-489a6480779f
next prev parent reply other threads:[~2025-02-04 21:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 17:13 [PATCH] linux/bits.h: Squash unsigned comparison warning for GENMASK Yazen Ghannam
2025-02-04 21:26 ` Yury Norov [this message]
2025-02-05 17:06 ` Yazen Ghannam
2025-02-05 20:59 ` Yury Norov
2025-02-06 2:02 ` Yazen Ghannam
2025-02-06 17:53 ` Yury Norov
2025-02-11 15:53 ` Vincent Mailhol
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=Z6KF8UBsQ4NmR9KS@thinkpad \
--to=yury.norov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=yazen.ghannam@amd.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