summaryrefslogtreecommitdiff
path: root/scripts/Makefile.thinlto
diff options
context:
space:
mode:
authorRicardo B. Marlière (SUSE) <ricardo@marliere.net>2026-10-14 15:00:52 -0300
committerSteven Rostedt <rostedt@goodmis.org>2026-10-20 14:18:37 -0400
commitbd1413cdee0b4a6b955a900d53ed3d8d085fbbbc (patch)
tree4a5d49bca93ce721c2e48c892dabb3553649cf12 /scripts/Makefile.thinlto
parentc03c1a14507dfaf8b856c2608f9ac216021fc222 (diff)
downloadlinux-bd1413cdee0b4a6b955a900d53ed3d8d085fbbbc.tar.gz
linux-bd1413cdee0b4a6b955a900d53ed3d8d085fbbbc.zip
ktest: Sort config keys before writing config files
apply_min_config(), save_config(), and make_min_config() write CONFIG_* lines by iterating "keys %hash" with no sort. Perl randomizes hash iteration order per process by default, so the line order of the resulting config files is not reproducible across otherwise identical invocations. When two of those lines are mutually exclusive members of the same Kconfig "choice", this can change which one "make olddefconfig" keeps, nondeterministically, from run to run. Observed with CONFIG_DEBUG_INFO_DWARF5 vs CONFIG_DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT: five consecutive "-C" builds from identical ADD_CONFIG/MIN_CONFIG inputs alternated between the two, which is enough to force a near-complete rebuild each time since CONFIG_DEBUG_INFO_* affects every object's compile flags. Sort the keys before writing so the same inputs always produce the same config output. Link: https://patch.msgid.link/20261014-ktest-kconfig-perl-hash-v1-1-66201a2dee82@marliere.net Signed-off-by: Ricardo B. Marlière (SUSE) <ricardo@marliere.net> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions