Re: kcsan -Wmaybe-uninitialized warning in ntfs3

Arnd Bergmann
2026-04-21T12:28:46Z

On Tue, Apr 21, 2026, at 13:35, Marco Elver wrote:
> On Tue, 21 Apr 2026 at 12:21, Arnd Bergmann <arnd@arndb.de> wrote:
>>
>> I ran into this during randconfig testing, I have attached a
>> reproducer .config here, but have not tried to narrow down the
>> configuration options that are required for triggering it.
>
> The attached .config is a KASAN config, still can't reproduce.

Odd, this is what I see in the attached file:

CONFIG_ARM64=y
CONFIG_KCSAN=y
CONFIG_KCSAN_SELFTEST=y
CONFIG_KCSAN_EARLY_ENABLE=y
CONFIG_KCSAN_NUM_WATCHPOINTS=64
CONFIG_KCSAN_UDELAY_TASK=80
CONFIG_KCSAN_UDELAY_INTERRUPT=20
# CONFIG_KCSAN_DELAY_RANDOMIZE is not set
CONFIG_KCSAN_SKIP_WATCH=4000
# CONFIG_KCSAN_SKIP_WATCH_RANDOMIZE is not set
CONFIG_KCSAN_INTERRUPT_WATCHER=y
CONFIG_KCSAN_REPORT_ONCE_IN_MS=3000
CONFIG_KCSAN_REPORT_RACE_UNKNOWN_ORIGIN=y
CONFIG_KCSAN_STRICT=y
# CONFIG_KASAN is not set
CONFIG_HAVE_ARCH_KFENCE=y
# CONFIG_KFENCE is not set
# end of Memory Debugging

I forgot to mention that the reproducer was on arm64, if you
tried building for x86, that may have messed up the config.

I've reverted my workaround in the randconfig tree now to see if
I can find a reproducer for x86 as well, in case that is easier.

Arnd