From: Helge Deller <deller@gmx.de>
To: Finn Thain <fthain@linux-m68k.org>
Cc: linux-parisc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] parisc: Drop linux/kernel.h include from asm/bug.h header
Date: Mon, 10 Nov 2025 11:23:13 +0100 [thread overview]
Message-ID: <7efd11f2-aa31-4ad5-bd07-18df750f53cf@gmx.de> (raw)
In-Reply-To: <3d812c89ecbc6028e3c550c484201f33d763b885.1762735489.git.fthain@linux-m68k.org>
On 11/10/25 01:44, Finn Thain wrote:
> While working on an unrelated patch series, I needed to include
> linux/bug.h from linux/instrumented.h, in order to call WARN_ON_ONCE().
>
> Doing so resulted in the following compiler error on parisc:
>
> In file included from ./include/linux/atomic/atomic-instrumented.h:17,
> from ./include/linux/atomic.h:82,
> from ./arch/parisc/include/asm/bitops.h:13,
> from ./include/linux/bitops.h:67,
> from ./include/linux/kernel.h:23,
> from ./arch/parisc/include/asm/bug.h:5,
> from ./include/linux/bug.h:5,
> from ./include/linux/page-flags.h:10,
> from kernel/bounds.c:10:
> ./include/linux/instrumented.h: In function 'instrument_atomic_alignment_check':
> ./include/linux/instrumented.h:69:9: error: implicit declaration of function 'WARN_ON_ONCE' [-Werror=implicit-function-declaration]
> 69 | WARN_ON_ONCE((unsigned long)v & (size - 1));
> | ^~~~~~~~~~~~
> cc1: some warnings being treated as errors
> make[3]: *** [scripts/Makefile.build:182: kernel/bounds.s] Error 1
>
> The problem is, asm/bug.h indirectly includes atomic-instrumented.h,
> which means a new cycle appeared in the graph of #includes. And because
> some headers in the cycle can't see all definitions, my new WARN_ON_ONCE()
> call appears to be an undeclared function.
>
> This only happens on parisc and it's easy to fix. In the error
> message above, linux/kernel.h is included by asm/bug.h, but it's no
> longer needed there, so just remove that include.
>
> The comment about needing BUGFLAG_TAINT seems to be incorrect as of
> commit 19d436268dde ("debug: Add _ONCE() logic to report_bug()"). Also,
> there's a comment in linux/kernel.h which strongly discourages use of
> that header.
>
> Compile-tested only.
>
> Acked-by: Helge Deller <deller@gmx.de> # parisc
> Signed-off-by: Finn Thain <fthain@linux-m68k.org>
> ---
> arch/parisc/include/asm/bug.h | 2 --
> 1 file changed, 2 deletions(-)
applied to parisc for-next git tree.
Thanks!
Helge
prev parent reply other threads:[~2025-11-10 10:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 0:44 Finn Thain
2025-11-10 10:23 ` Helge Deller [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=7efd11f2-aa31-4ad5-bd07-18df750f53cf@gmx.de \
--to=deller@gmx.de \
--cc=fthain@linux-m68k.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®