summaryrefslogtreecommitdiff
path: root/tools/testing/selftests/bpf/prog_tests/autoload.c
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2025-08-07 10:21:28 +0300
committerOliver Upton <oliver.upton@linux.dev>2025-08-08 11:28:57 +0300
commit700d6868fee2d384cbd821d31db3a245d218223c (patch)
tree557db37fc198a94765321a2bc078f57d17cd051b /tools/testing/selftests/bpf/prog_tests/autoload.c
parent69f8fe955d0b4a951c3726669ab58360ed562484 (diff)
downloadlinux-700d6868fee2d384cbd821d31db3a245d218223c.tar.xz
kvm: arm64: use BUG() instead of BUG_ON(1)
The BUG_ON() macro adds a little bit of complexity over BUG(), and in some cases this ends up confusing the compiler's control flow analysis in a way that results in a warning. This one now shows up with clang-21: arch/arm64/kvm/vgic/vgic-mmio.c:1094:3: error: variable 'len' is used uninitialized whenever 'if' condition is false [-Werror,-Wsometimes-uninitialized] 1094 | BUG_ON(1); Change both instances of BUG_ON(1) to a plain BUG() in the arm64 kvm code, to avoid the false-positive warning. Signed-off-by: Arnd Bergmann <arnd@arndb.de> Reviewed-by: Nathan Chancellor <nathan@kernel.org> Link: https://lore.kernel.org/r/20250807072132.4170088-1-arnd@kernel.org Signed-off-by: Oliver Upton <oliver.upton@linux.dev>
Diffstat (limited to 'tools/testing/selftests/bpf/prog_tests/autoload.c')
0 files changed, 0 insertions, 0 deletions