linux-kernel - [REGRESSION] (build) kallsyms.h:21:10: fatal error: execinfo.h: No such file or directory

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>] [day] [month] [year] [list]

Message-ID: <20250701161309.0f7984c3@ncopa-desktop>
Date: Tue, 1 Jul 2025 16:13:09 +0200
From: Natanael Copa <ncopa@...inelinux.org>
To: linux-kernel@...r.kernel.org
Cc: Andrew Morton <akpm@...ux-foundation.org>, Linus Torvalds
 <torvalds@...ux-foundation.org>, Achill Gilgenast <fossdd@...ed.life>
Subject: [REGRESSION]  (build) kallsyms.h:21:10: fatal error: execinfo.h: No
 such file or directory

Hi!

Commit c104c16073b7 (Kunit to check the longest symbol length)
introduced a regression that causes build to fail on musl libc systems.
The regression has now tickled down to stable releases and is currently
blocking kernel upgrades for Alpine Linux.

There was a fix proposed[1] which has not yet been applied, and Greg
asked us to get the fix (or revert?) in upstream first before handling
it for stable[2].

Since it appears to take some time to get this fixed, I wonder if
we can revert commit c104c16073b7 (Kunit to check the longest symbol
length) til someone has time to help us work out an acceptable fix?

Thanks!

-nc

[1]: https://lore.kernel.org/stable/DB0OSTC6N4TL.2NK75K2CWE9JV@pwned.life/T/#t
[2]: https://lore.kernel.org/stable/2025070104-ether-wipe-9c19@gregkh/