* [arm64:for-next/core 12/12] usr/include/asm/sigcontext.h:81:9: error: unknown type name '__u128'; did you mean '__u32'?
@ 2026-06-24 2:14 kernel test robot
0 siblings, 0 replies; only message in thread
From: kernel test robot @ 2026-06-24 2:14 UTC (permalink / raw)
To: Will Deacon; +Cc: oe-kbuild-all, linux-arm-kernel, Marc Zyngier, Arnd Bergmann
Hi Will,
FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core
head: 9d6306113f921dc00793df46f31ed46583c720df
commit: 9d6306113f921dc00793df46f31ed46583c720df [12/12] arm64: uapi: Use __u128 instead of __uint128_t in UAPI headers
config: arm64-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260624/202606240441.7eZ1TIRM-lkp@intel.com/config)
compiler: aarch64-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260624/202606240441.7eZ1TIRM-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202606240441.7eZ1TIRM-lkp@intel.com/
Note: the arm64/for-next/core HEAD 9d6306113f921dc00793df46f31ed46583c720df builds fine.
It only hurts bisectability.
All errors (new ones prefixed by >>):
In file included from /usr/aarch64-linux-gnu/include/bits/sigcontext.h:30,
from /usr/aarch64-linux-gnu/include/signal.h:301,
from testcases/fake_sigreturn_bad_magic.c:10:
>> usr/include/asm/sigcontext.h:81:9: error: unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~
| __u32
In file included from ./test_signals.h:14,
from ./test_signals_utils.h:14,
from testcases/fake_sigreturn_bad_magic.c:13:
>> usr/include/asm/ptrace.h:96:9: error: unknown type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:261:9: error: unknown type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:262:9: error: unknown type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:263:9: error: unknown type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:264:9: error: unknown type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:268:9: error: unknown type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~
| __u32
In file included from /usr/aarch64-linux-gnu/include/bits/sigcontext.h:30,
from /usr/aarch64-linux-gnu/include/signal.h:301,
from test_signals.h:7,
from test_signals.c:16:
>> usr/include/asm/sigcontext.h:81:9: error: unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~
| __u32
In file included from test_signals.h:14:
>> usr/include/asm/ptrace.h:96:9: error: unknown type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:261:9: error: unknown type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:262:9: error: unknown type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:263:9: error: unknown type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:264:9: error: unknown type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:268:9: error: unknown type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~
| __u32
In file included from /usr/aarch64-linux-gnu/include/bits/sigcontext.h:30,
from /usr/aarch64-linux-gnu/include/signal.h:301,
from test_signals_utils.c:6:
>> usr/include/asm/sigcontext.h:81:9: error: unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~
| __u32
In file included from test_signals.h:14,
from test_signals_utils.c:18:
>> usr/include/asm/ptrace.h:96:9: error: unknown type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:261:9: error: unknown type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:262:9: error: unknown type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:263:9: error: unknown type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:264:9: error: unknown type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:268:9: error: unknown type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~
| __u32
In file included from /usr/aarch64-linux-gnu/include/bits/sigcontext.h:30,
from /usr/aarch64-linux-gnu/include/signal.h:301,
from testcases/testcases.h:12,
from testcases/testcases.c:7:
>> usr/include/asm/sigcontext.h:81:9: error: unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~
| __u32
In file included from sve_helpers.c:10:
>> usr/include/asm/sigcontext.h:81:9: error: unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~
| __u32
--
In file included from /usr/aarch64-linux-gnu/include/bits/sigcontext.h:30,
from /usr/aarch64-linux-gnu/include/signal.h:301,
from /usr/aarch64-linux-gnu/include/sys/wait.h:36,
from pac.c:8:
>> usr/include/asm/sigcontext.h:81:9: error: unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~
| __u32
--
In file included from /usr/aarch64-linux-gnu/include/bits/sigcontext.h:30,
from /usr/aarch64-linux-gnu/include/signal.h:301,
from /usr/aarch64-linux-gnu/include/sys/wait.h:36,
from fp-ptrace.c:22:
>> usr/include/asm/sigcontext.h:81:9: error: unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~
| __u32
In file included from fp-ptrace.c:28:
>> usr/include/asm/ptrace.h:96:9: error: unknown type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:261:9: error: unknown type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:262:9: error: unknown type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:263:9: error: unknown type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:264:9: error: unknown type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:268:9: error: unknown type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~
| __u32
--
In file included from /usr/aarch64-linux-gnu/include/bits/sigcontext.h:30,
from /usr/aarch64-linux-gnu/include/signal.h:301,
from mte_common_util.h:7,
from check_buffer_fill.c:11:
>> usr/include/asm/sigcontext.h:81:9: error: unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~
| __u32
In file included from /usr/aarch64-linux-gnu/include/bits/sigcontext.h:30,
from /usr/aarch64-linux-gnu/include/signal.h:301,
from mte_common_util.c:6:
>> usr/include/asm/sigcontext.h:81:9: error: unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~
| __u32
--
In file included from system.h:20,
from test.c:7:
>> usr/include/asm/ptrace.h:96:9: error: unknown type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:261:9: error: unknown type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:262:9: error: unknown type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:263:9: error: unknown type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:264:9: error: unknown type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:268:9: error: unknown type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~
| __u32
In file included from test.c:14:
>> usr/include/asm/sigcontext.h:81:9: error: unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~
| __u32
--
In file included from system.h:20,
from signal.c:7:
>> usr/include/asm/ptrace.h:96:9: error: unknown type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:261:9: error: unknown type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:262:9: error: unknown type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:263:9: error: unknown type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:264:9: error: unknown type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:268:9: error: unknown type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~
| __u32
--
In file included from /usr/aarch64-linux-gnu/include/bits/sigcontext.h:30,
from /usr/aarch64-linux-gnu/include/signal.h:301,
from tools/testing/selftests/cgroup/lib/cgroup_util.c:9:
>> usr/include/asm/sigcontext.h:81:9: error: unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~
| __u32
cc1: note: unrecognized command-line option '-Wno-gnu-variable-sized-type-not-at-end' may have been intended to silence earlier diagnostics
--
In file included from /usr/aarch64-linux-gnu/include/bits/sigcontext.h:30,
from /usr/aarch64-linux-gnu/include/signal.h:301,
from include/test_util.h:12,
from include/kvm_util.h:8,
from demand_paging_test.c:17:
>> usr/include/asm/sigcontext.h:81:9: error: unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~
| __u32
In file included from usr/include/asm/kvm.h:37,
from usr/include/linux/kvm.h:16,
from include/kvm_util.h:14:
>> usr/include/asm/ptrace.h:96:9: error: unknown type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:261:9: error: unknown type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:262:9: error: unknown type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:263:9: error: unknown type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:264:9: error: unknown type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:268:9: error: unknown type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~
| __u32
cc1: note: unrecognized command-line option '-Wno-gnu-variable-sized-type-not-at-end' may have been intended to silence earlier diagnostics
--
In file included from usr/include/asm/kvm.h:37,
from usr/include/linux/kvm.h:16,
from lib/arm64/gic_v3_its.c:7:
>> usr/include/asm/ptrace.h:96:9: error: unknown type name '__u128'; did you mean '__u32'?
96 | __u128 vregs[32];
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:261:9: error: unknown type name '__u128'; did you mean '__u32'?
261 | __u128 apiakey;
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:262:9: error: unknown type name '__u128'; did you mean '__u32'?
262 | __u128 apibkey;
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:263:9: error: unknown type name '__u128'; did you mean '__u32'?
263 | __u128 apdakey;
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:264:9: error: unknown type name '__u128'; did you mean '__u32'?
264 | __u128 apdbkey;
| ^~~~~~
| __u32
usr/include/asm/ptrace.h:268:9: error: unknown type name '__u128'; did you mean '__u32'?
268 | __u128 apgakey;
| ^~~~~~
| __u32
In file included from /usr/aarch64-linux-gnu/include/bits/sigcontext.h:30,
from /usr/aarch64-linux-gnu/include/signal.h:301,
from include/test_util.h:12,
from include/kvm_util.h:8,
from lib/arm64/gic_v3_its.c:12:
>> usr/include/asm/sigcontext.h:81:9: error: unknown type name '__u128'; did you mean '__u32'?
81 | __u128 vregs[32];
| ^~~~~~
| __u32
cc1: note: unrecognized command-line option '-Wno-gnu-variable-sized-type-not-at-end' may have been intended to silence earlier diagnostics
..
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2026-06-24 2:15 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-06-24 2:14 [arm64:for-next/core 12/12] usr/include/asm/sigcontext.h:81:9: error: unknown type name '__u128'; did you mean '__u32'? kernel test robot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox