d13bad83d89d1022fee254c08f6e01084eb4395e - kconfig: check for hex and int mismatches

Tue, 15 Sep 2026 23:15:06 +0200

kconfig: check for hex and int mismatchesUsing a numeric option of one type (e.g. 'int') to determine the value ofa different numeric type (e.g. 'hex') currently fails silently in variousways if attempted, because the underlying string representation is naivelyreused.Example 1: config I int default -1 config HEX_DEFAULT_INT hex default IHere, HEX_DEFAULT_INT actually gets set to '0x-1', which is of course nota valid hex value.Example 2: config H hex default A config INT_DEFAULT_HEX int default HHere, INT_DEFAULT_HEX actually gets set to 'A', without even convertinginto the base-10 equivalent of 10. This value, 'A', is otherwise arejected int value if entered in the frontend, or read in from an existing.config file.These int-hex mismatches currently do not appear anywhere in the tree, soit is already safe to make these error out.Assisted-by: LLMSigned-off-by: Julian Braha Reviewed-by: Nicolas Schier Link: https://patch.msgid.link/20260915211508.291790-4-julianbraha@gmail.comSigned-off-by: Nathan Chancellor List of files: /linux/scripts/kconfig/tests/err_num_mismatch/expected_stderr

Changes in expected_stderr

d13bad83d89d1022fee254c08f6e01084eb4395e - kconfig: check for hex and int mismatches