From: Helge Deller <deller@gmx.de>
To: Kees Cook <kees@kernel.org>, linux-arch@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-parisc@vger.kernel.org
Subject: Re: [PATCH 13/17] parisc: Add __attribute_const__ to ffs()-family implementations
Date: Fri, 8 Aug 2025 11:01:32 +0200 [thread overview]
Message-ID: <aa0d0695-5af4-4986-b6ea-24dd2da9f747@gmx.de> (raw)
In-Reply-To: <20250804164417.1612371-13-kees@kernel.org>
On 8/4/25 18:44, Kees Cook wrote:
> While tracking down a problem where constant expressions used by
> BUILD_BUG_ON() suddenly stopped working[1], we found that an added static
> initializer was convincing the compiler that it couldn't track the state
> of the prior statically initialized value. Tracing this down found that
> ffs() was used in the initializer macro, but since it wasn't marked with
> __attribute__const__, the compiler had to assume the function might
> change variable states as a side-effect (which is not true for ffs(),
> which provides deterministic math results).
>
> Add missing __attribute_const__ annotations to PARISC's implementations of
> ffs(), __ffs(), and fls() functions. These are pure mathematical functions
> that always return the same result for the same input with no side effects,
> making them eligible for compiler optimization.
>
> Build tested ARCH=parisc defconfig with GCC hppa-linux-gnu 14.2.0.
>
> Link: https://github.com/KSPP/linux/issues/364 [1]
> Signed-off-by: Kees Cook <kees@kernel.org>
> ---
> arch/parisc/include/asm/bitops.h | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
Acked-by: Helge Deller <deller@gmx.de>
next prev parent reply other threads:[~2025-08-08 9:01 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 16:43 [PATCH 00/17] " Kees Cook
2025-08-04 16:43 ` [PATCH 01/17] KUnit: Introduce ffs()-family tests Kees Cook
2025-08-04 16:43 ` [PATCH 02/17] bitops: Add __attribute_const__ to generic ffs()-family implementations Kees Cook
2025-08-04 16:43 ` [PATCH 03/17] csky: Add __attribute_const__ to " Kees Cook
2025-10-19 6:50 ` Guo Ren
2025-08-04 16:44 ` [PATCH 04/17] x86: " Kees Cook
2025-08-04 16:44 ` [PATCH 05/17] powerpc: " Kees Cook
2025-08-07 9:46 ` Madhavan Srinivasan
2025-08-15 16:34 ` Segher Boessenkool
2025-08-15 16:41 ` Segher Boessenkool
2025-08-04 16:44 ` [PATCH 06/17] sh: " Kees Cook
2025-08-04 16:44 ` [PATCH 07/17] alpha: " Kees Cook
2025-08-04 16:44 ` [PATCH 08/17] hexagon: " Kees Cook
2025-08-04 16:44 ` [PATCH 09/17] riscv: " Kees Cook
2025-08-07 14:43 ` Alexandre Ghiti
2025-08-04 16:44 ` [PATCH 10/17] openrisc: " Kees Cook
2025-08-04 17:15 ` Stafford Horne
2025-08-04 16:44 ` [PATCH 11/17] m68k: " Kees Cook
2025-08-05 8:12 ` Geert Uytterhoeven
2025-08-04 16:44 ` [PATCH 12/17] mips: " Kees Cook
2025-08-04 16:44 ` [PATCH 13/17] parisc: " Kees Cook
2025-08-08 9:01 ` Helge Deller [this message]
2025-08-04 16:44 ` [PATCH 14/17] s390: " Kees Cook
2025-08-06 10:33 ` Heiko Carstens
2025-08-04 16:44 ` [PATCH 15/17] xtensa: " Kees Cook
2025-08-04 16:44 ` [PATCH 16/17] sparc: " Kees Cook
2025-08-04 16:44 ` [PATCH 17/17] KUnit: ffs: Validate all the __attribute_const__ annotations Kees Cook
2025-08-15 14:16 ` [PATCH 00/17] Add __attribute_const__ to ffs()-family implementations Peter Zijlstra
2025-10-09 1:07 ` patchwork-bot+linux-riscv
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=aa0d0695-5af4-4986-b6ea-24dd2da9f747@gmx.de \
--to=deller@gmx.de \
--cc=kees@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@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
all inboxes | Powered by JetHome®