On Wed, 24 Jan 2024 18:31:34 +0100 Alexander Potapenko <glider@xxxxxxxxxx> wrote:
> Similarly to what's been done in commit ff444efbbb9be ("kmsan: allow
I make that 85716a80c16d.
> using __msan_instrument_asm_store() inside runtime"), it should be safe
> to call kmsan_unpoison_memory() from within the runtime, as it does not
> allocate memory or take locks. Remove the redundant runtime checks.
>
> This should fix false positives seen with CONFIG_DEBUG_LIST=y when
> the non-instrumented lib/stackdepot.c failed to unpoison the memory
> chunks later checked by the instrumented lib/list_debug.c
>
> Also replace the implementation of kmsan_unpoison_entry_regs() with
> a call to kmsan_unpoison_memory().
>
"false positives" sound unpleasant. Should this fix be backported into
earlier kernels? And can we identify a suitable Fixes: target?
