Module: linux-5.17/drivers/mtd/nand/raw/nand_base.c Function: nand_match_ecc_req() Observation: compiler exits with error because local variables best_step and best_ecc_bytes are not pre-initialized to "0". Root cause: if the for loop is not executed the record entries chip->ecc.size and chip->ecc.bytes will be initialized with random stack values. This leads to unpredictable mal-function of the function caller. Interesting: clang-15.0.0 is not complaining
Is this already in earlier kernels like 5.16 or new in 5.17?
I use in meantime kernel 6.1.1. and topic is likely gone. My mitigation to get freed from the many warnings if compiling with "gcc (GCC) 13.0.0" and/or clang version 16.0.0: --> Commenting out "KBUILD_CFLAGS-$(CONFIG_WERROR) += -Werror" With kernel 6.1.1 the -Werror instruction can stay active and no warnings popping up.