From: Yury Norov <yury.norov@gmail.com>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
Vincent Mailhol <mailhol.vincent@wanadoo.fr>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] uapi: bitops: use UAPI-safe variant of BITS_PER_LONG again (2)
Date: Mon, 30 Jun 2025 10:52:51 -0400 [thread overview]
Message-ID: <aGKkw6b1QPTf9yii@yury> (raw)
In-Reply-To: <20250630-uapi-genmask-v1-1-eb0ad956a83e@linutronix.de>
On Mon, Jun 30, 2025 at 03:02:18PM +0200, Thomas Weißschuh wrote:
> BITS_PER_LONG does not exist in UAPI headers, so can't be used by the UAPI
> __GENMASK(). Instead __BITS_PER_LONG needs to be used.
>
> When __GENMASK() was introduced in commit 3c7a8e190bc5 ("uapi: introduce uapi-friendly macros for GENMASK"),
> the code was fine. A broken revert in 1e7933a575ed ("uapi: Revert "bitops: avoid integer overflow in GENMASK(_ULL)"")
> introduced the incorrect usage of BITS_PER_LONG.
> That was fixed in commit 11fcf368506d ("uapi: bitops: use UAPI-safe variant of BITS_PER_LONG again").
> But a broken sync of the kernel headers with the tools/ headers in
> commit fc92099902fb ("tools headers: Synchronize linux/bits.h with the kernel sources")
> undid the fix.
>
> Reapply the fix and while at it also fix the tools header.
>
> Fixes: fc92099902fb ("tools headers: Synchronize linux/bits.h with the kernel sources")
> Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
Acked-by: Yury Norov (NVIDIA) <yury.norov@gmail.com>
Arnaldo, do you want to move it yourself or with my branch?
> ---
> include/uapi/linux/bits.h | 4 ++--
> tools/include/uapi/linux/bits.h | 4 ++--
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/include/uapi/linux/bits.h b/include/uapi/linux/bits.h
> index 682b406e10679dc8baa188830ab0811e7e3e13e3..a04afef9efca42f062e142fcb33f5d267512b1e5 100644
> --- a/include/uapi/linux/bits.h
> +++ b/include/uapi/linux/bits.h
> @@ -4,9 +4,9 @@
> #ifndef _UAPI_LINUX_BITS_H
> #define _UAPI_LINUX_BITS_H
>
> -#define __GENMASK(h, l) (((~_UL(0)) << (l)) & (~_UL(0) >> (BITS_PER_LONG - 1 - (h))))
> +#define __GENMASK(h, l) (((~_UL(0)) << (l)) & (~_UL(0) >> (__BITS_PER_LONG - 1 - (h))))
>
> -#define __GENMASK_ULL(h, l) (((~_ULL(0)) << (l)) & (~_ULL(0) >> (BITS_PER_LONG_LONG - 1 - (h))))
> +#define __GENMASK_ULL(h, l) (((~_ULL(0)) << (l)) & (~_ULL(0) >> (__BITS_PER_LONG_LONG - 1 - (h))))
>
> #define __GENMASK_U128(h, l) \
> ((_BIT128((h)) << 1) - (_BIT128(l)))
> diff --git a/tools/include/uapi/linux/bits.h b/tools/include/uapi/linux/bits.h
> index 682b406e10679dc8baa188830ab0811e7e3e13e3..a04afef9efca42f062e142fcb33f5d267512b1e5 100644
> --- a/tools/include/uapi/linux/bits.h
> +++ b/tools/include/uapi/linux/bits.h
> @@ -4,9 +4,9 @@
> #ifndef _UAPI_LINUX_BITS_H
> #define _UAPI_LINUX_BITS_H
>
> -#define __GENMASK(h, l) (((~_UL(0)) << (l)) & (~_UL(0) >> (BITS_PER_LONG - 1 - (h))))
> +#define __GENMASK(h, l) (((~_UL(0)) << (l)) & (~_UL(0) >> (__BITS_PER_LONG - 1 - (h))))
>
> -#define __GENMASK_ULL(h, l) (((~_ULL(0)) << (l)) & (~_ULL(0) >> (BITS_PER_LONG_LONG - 1 - (h))))
> +#define __GENMASK_ULL(h, l) (((~_ULL(0)) << (l)) & (~_ULL(0) >> (__BITS_PER_LONG_LONG - 1 - (h))))
>
> #define __GENMASK_U128(h, l) \
> ((_BIT128((h)) << 1) - (_BIT128(l)))
>
> ---
> base-commit: d0b3b7b22dfa1f4b515fd3a295b3fd958f9e81af
> change-id: 20250630-uapi-genmask-d36e3ffc5691
>
> Best regards,
> --
> Thomas Weißschuh <thomas.weissschuh@linutronix.de>
next prev parent reply other threads:[~2025-06-30 14:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 13:02 [PATCH] uapi: bitops: use UAPI-safe variant of BITS_PER_LONG again (2) Thomas Weißschuh
2025-06-30 14:52 ` Yury Norov [this message]
2025-07-01 21:37 ` Yury Norov
2025-07-08 6:26 ` Thomas Weißschuh
2025-07-08 14:47 ` Yury Norov
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=aGKkw6b1QPTf9yii@yury \
--to=yury.norov@gmail.com \
--cc=acme@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mailhol.vincent@wanadoo.fr \
--cc=thomas.weissschuh@linutronix.de \
/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