From: KernelCI bot <bot@kernelci.org>
To: kernelci-results@groups.io
Cc: gus@collabora.com, rppt@kernel.org, linux-mm@kvack.org
Subject: [REGRESSION] rppt/for-kernelci: (build) call to '__compiletime_assert_295' declared with 'error' attribute...
Date: Tue, 25 Nov 2025 02:59:11 -0000 [thread overview]
Message-ID: <176403955165.358.6256582403213124388@f771fd7c9232> (raw)
Hello,
New build issue found on rppt/for-kernelci:
---
call to '__compiletime_assert_295' declared with 'error' attribute: BUILD_BUG_ON failed: sizeof(_s) > sizeof(long) in drivers/ata/libahci.o (drivers/ata/libahci.c) [logspec:kbuild,kbuild.compiler.error]
---
- dashboard: https://d.kernelci.org/i/maestro:93960d0b3e4b52513b908bcfe11a9e01571331de
- giturl: https://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock.git
- commit HEAD: 7a1b17aedd2aad3a04a211865f048903bd47fedd
Log excerpt:
=====================================================
drivers/ata/libahci.c:1161:9: error: call to '__compiletime_assert_295' declared with 'error' attribute: BUILD_BUG_ON failed: sizeof(_s) > sizeof(long)
1161 | pmp = array_index_nospec(pmp, EM_MAX_SLOTS);
| ^
./include/linux/nospec.h:58:2: note: expanded from macro 'array_index_nospec'
58 | BUILD_BUG_ON(sizeof(_s) > sizeof(long)); \
| ^
./include/linux/build_bug.h:50:2: note: expanded from macro 'BUILD_BUG_ON'
50 | BUILD_BUG_ON_MSG(condition, "BUILD_BUG_ON failed: " #condition)
| ^
./include/linux/build_bug.h:39:37: note: expanded from macro 'BUILD_BUG_ON_MSG'
39 | #define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg)
| ^
note: (skipping 1 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
././include/linux/compiler_types.h:340:2: note: expanded from macro '_compiletime_assert'
340 | __compiletime_assert(condition, msg, prefix, suffix)
| ^
././include/linux/compiler_types.h:333:4: note: expanded from macro '__compiletime_assert'
333 | prefix ## suffix(); \
| ^
<scratch space>:171:1: note: expanded from here
171 | __compiletime_assert_295
| ^
1 error generated.
=====================================================
# Builds where the incident occurred:
## multi_v7_defconfig on (arm):
- compiler: clang-21
- config: https://files.kernelci.org/kbuild-clang-21-arm-6924fce9f5b8743b1f5fa54c/.config
- dashboard: https://d.kernelci.org/build/maestro:6924fce9f5b8743b1f5fa54c
#kernelci issue maestro:93960d0b3e4b52513b908bcfe11a9e01571331de
Reported-by: kernelci.org bot <bot@kernelci.org>
--
This is an experimental report format. Please send feedback in!
Talk to us at kernelci@lists.linux.dev
Made with love by the KernelCI team - https://kernelci.org
reply other threads:[~2025-11-25 2:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=176403955165.358.6256582403213124388@f771fd7c9232 \
--to=bot@kernelci.org \
--cc=gus@collabora.com \
--cc=kernelci-results@groups.io \
--cc=kernelci@lists.linux.dev \
--cc=linux-mm@kvack.org \
--cc=rppt@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