linux-kernel - Re: next: clang-15: s390x-linux-gnu-ld: BFD (GNU Binutils for Debian) 2.35.2 assertion fail ../../bfd/elf64-s390.c:3349

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <Y7cRJ8xh/LLT9kk0@dev-arch.thelio-3990X>
Date:   Thu, 5 Jan 2023 11:04:23 -0700
From:   Nathan Chancellor <nathan@...nel.org>
To:     Naresh Kamboju <naresh.kamboju@...aro.org>
Cc:     linux-s390@...r.kernel.org,
        open list <linux-kernel@...r.kernel.org>,
        Linux-Next Mailing List <linux-next@...r.kernel.org>,
        lkft-triage@...ts.linaro.org, llvm@...ts.linux.dev,
        Heiko Carstens <hca@...ux.ibm.com>,
        Vasily Gorbik <gor@...ux.ibm.com>,
        Christian Borntraeger <borntraeger@...ux.ibm.com>
Subject: Re: next: clang-15: s390x-linux-gnu-ld: BFD (GNU Binutils for
 Debian) 2.35.2 assertion fail ../../bfd/elf64-s390.c:3349

Hi Naresh,

On Thu, Jan 05, 2023 at 10:19:23PM +0530, Naresh Kamboju wrote:
> The s390 clang-15 build failures on Linux next-20230105 due to following
> errors / warnings.
> 
> Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
> 
> `.exit.text' referenced in section `__jump_table' of fs/fuse/inode.o:
> defined in discarded section `.exit.text' of fs/fuse/inode.o
> `.exit.text' referenced in section `__jump_table' of fs/fuse/inode.o:
> defined in discarded section `.exit.text' of fs/fuse/inode.o
> `.exit.text' referenced in section `__bug_table' of crypto/algboss.o:
> defined in discarded section `.exit.text' of crypto/algboss.o
> `.exit.text' referenced in section `__bug_table' of drivers/scsi/sd.o:
> defined in discarded section `.exit.text' of drivers/scsi/sd.o
> `.exit.text' referenced in section `__jump_table' of drivers/md/md.o:
> defined in discarded section `.exit.text' of drivers/md/md.o
> `.exit.text' referenced in section `__jump_table' of drivers/md/md.o:
> defined in discarded section `.exit.text' of drivers/md/md.o
> `.exit.text' referenced in section `.altinstructions' of
> drivers/md/md.o: defined in discarded section `.exit.text' of
> drivers/md/md.o
> `.exit.text' referenced in section `.altinstructions' of
> drivers/md/md.o: defined in discarded section `.exit.text' of
> drivers/md/md.o
> `.exit.text' referenced in section `.altinstructions' of
> net/iucv/iucv.o: defined in discarded section `.exit.text' of
> net/iucv/iucv.o
> `.exit.text' referenced in section `__bug_table' of
> drivers/s390/cio/qdio_thinint.o: defined in discarded section
> `.exit.text' of drivers/s390/cio/qdio_thinint.o
> `.exit.text' referenced in section `__bug_table' of
> drivers/s390/net/qeth_l3_main.o: defined in discarded section
> `.exit.text' of drivers/s390/net/qeth_l3_main.o
> `.exit.text' referenced in section `__bug_table' of
> drivers/s390/net/qeth_l3_main.o: defined in discarded section
> `.exit.text' of drivers/s390/net/qeth_l3_main.o
> s390x-linux-gnu-ld: BFD (GNU Binutils for Debian) 2.35.2 assertion
> fail ../../bfd/elf64-s390.c:3349
> make[2]: *** [scripts/Makefile.vmlinux:34: vmlinux] Error 1
> make[2]: Target '__default' not remade because of errors.
> make[1]: *** [Makefile:1252: vmlinux] Error 2

Thank you for the report! This has been reported and discussed in a few
different places on the mailing list with various solutions:

https://lore.kernel.org/Y7Jal56f6UBh1abE@dev-arch.thelio-3990X/
https://lore.kernel.org/20230102225656.GA3532398@roeck-us.net/

https://lore.kernel.org/20230105031306.1455409-1-masahiroy@kernel.org/
https://lore.kernel.org/20230105132349.384666-1-mpe@ellerman.id.au/
https://lore.kernel.org/CAMj1kXHqQoqoys83nEp=Q6oT68+-GpCuMjfnYK9pMy-X_+jjKw@mail.gmail.com/

For the future, if you are able to bisect to the change that caused the
failure, you can devise a more targeted Cc list and potentially find
some of this information out beforehand, which would allow more threads
to stay together.

The PowerPC build failure that you reported around the same time as this
one has the same root cause.

Cheers,
Nathan