linux-kernel - Re: [Regression in 6.19-rc6] Build breakage after commit 436326bc525d

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAJZ5v0i6Uw0+L5SY3QW+py82uEVktNWcHGHf=Za96mQpN7X8Bw@mail.gmail.com>
Date: Tue, 20 Jan 2026 19:29:58 +0100
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Sasha Levin <sashal@...nel.org>
Cc: Peter Zijlstra <peterz@...radead.org>, "Rafael J. Wysocki" <rafael@...nel.org>, 
	Josh Poimboeuf <jpoimboe@...hat.com>, Arnaldo Carvalho de Melo <acme@...nel.org>, 
	"the arch/x86 maintainers" <x86@...nel.org>, Linus Torvalds <torvalds@...ux-foundation.org>, 
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, 
	Linux regressions mailing list <regressions@...ts.linux.dev>, irogers@...gle.com
Subject: Re: [Regression in 6.19-rc6] Build breakage after commit 436326bc525d

On Tue, Jan 20, 2026 at 6:40 PM Sasha Levin <sashal@...nel.org> wrote:
>
> On Tue, Jan 20, 2026 at 11:28:32AM +0100, Peter Zijlstra wrote:
> >On Mon, Jan 19, 2026 at 09:19:31PM +0100, Rafael J. Wysocki wrote:
> >> Hi Sasha,
> >>
> >> Commit 436326bc525d ("objtool: fix build failure due to missing
> >> libopcodes check") breaks kernel build for me.
> >>
> >> Here's what I get when I try to build the kernel after that commit:
> >>
> >>   LD      /scratch/rafael/work/build/xps13/tools/objtool/objtool-in.o
> >>   LINK    /scratch/rafael/work/build/xps13/tools/objtool/objtool
> >> /usr/lib64/gcc/x86_64-suse-linux/15/../../../../x86_64-suse-linux/bin/ld:
> >> /usr/lib64/gcc/x86_64-suse-linux/15/../../../../lib64/libopcodes.a(aarch64-dis.o):
> >> in function `print_operands':
> >> /home/abuild/rpmbuild/BUILD/binutils-2.45/build-dir/opcodes/../../opcodes/aarch64-dis.c:3945:(.text+0x6317):
> >> undefined reference to `xmalloc'
> >> /usr/lib64/gcc/x86_64-suse-linux/15/../../../../x86_64-suse-linux/bin/ld:
> >> /home/abuild/rpmbuild/BUILD/binutils-2.45/build-dir/opcodes/../../opcodes/aarch64-dis.c:3992:(.text+0x6723):
> >> undefined reference to `_sch_istable'
> >> /usr/lib64/gcc/x86_64-suse-linux/15/../../../../x86_64-suse-linux/bin/ld:
> >> /usr/lib64/gcc/x86_64-suse-linux/15/../../../../lib64/libopcodes.a(aarch64-dis.o):
> >> in function `print_insn_aarch64':
> >> /home/abuild/rpmbuild/BUILD/binutils-2.45/build-dir/opcodes/../../opcodes/aarch64-dis.c:4559:(.text+0x6b1e):
> >> undefined reference to `bfd_get_bits'
> >> /usr/lib64/gcc/x86_64-suse-linux/15/../../../../x86_64-suse-linux/bin/ld:
> >> /usr/lib64/gcc/x86_64-suse-linux/15/../../../../lib64/libopcodes.a(aarch64-dis.o):
> >> in function `parse_aarch64_dis_option':
> >> /home/abuild/rpmbuild/BUILD/binutils-2.45/build-dir/opcodes/../../opcodes/aarch64-dis.c:103:(.text+0x6dea):
> >> undefined reference to `_bfd_error_handler'
> >> /usr/lib64/gcc/x86_64-suse-linux/15/../../../../x86_64-suse-linux/bin/ld:
> >> /usr/lib64/gcc/x86_64-suse-linux/15/../../../../lib64/libopcodes.a(aarch64-opc.o):
> >> in function `init_insn_sequence':
> >> /home/abuild/rpmbuild/BUILD/binutils-2.45/build-dir/opcodes/../../opcodes/aarch64-opc.c:5561:(.text+0x5c06):
> >> undefined reference to `xcalloc'
> >> /usr/lib64/gcc/x86_64-suse-linux/15/../../../../x86_64-suse-linux/bin/ld:
> >> /usr/lib64/gcc/x86_64-suse-linux/15/../../../../lib64/libopcodes.a(disassemble.o):
> >> in function `remove_whitespace_and_extra_commas':
> >> /home/abuild/rpmbuild/BUILD/binutils-2.45/build-dir/opcodes/../../opcodes/disassemble.c:801:(.text+0x346):
> >> undefined reference to `_sch_istable'
> >> ...
> >>
> >> (many more similar messages skipped).
> >>
> >> Reverting commit 436326bc525d makes the problem go away.
>
> Thanks for the report Rafael!
>
> Could you confirm that you're linking against static libraries? I haven't
> tested that scenario.

How do I check that?