diff options
| author | Alexander Potapenko <[email protected]> | 2022-11-28 10:45:41 +0100 |
|---|---|---|
| committer | Andrew Morton <[email protected]> | 2022-12-11 18:12:11 -0800 |
| commit | 85716a80c16dd6b6d1aaed87cd4b91c9b1d9b9b2 (patch) | |
| tree | 903afb31d5696113fb7901bb70fd57a834f67e12 /tools/perf/scripts/python/syscall-counts.py | |
| parent | 1e8e4a7cc2fa3017b1daf02612e095d51924ce1e (diff) | |
kmsan: allow using __msan_instrument_asm_store() inside runtime
In certain cases (e.g. when handling a softirq)
__msan_instrument_asm_store(&var, sizeof(var)) may be called with from
within KMSAN runtime, but later the value of @var is used with
!kmsan_in_runtime(), leading to false positives.
Because kmsan_internal_unpoison_memory() doesn't take locks, it should be
fine to call it without kmsan_in_runtime() checks, which fixes the
mentioned false positives.
Link: https://lkml.kernel.org/r/[email protected]
Signed-off-by: Alexander Potapenko <[email protected]>
Cc: Dmitry Vyukov <[email protected]>
Cc: Eric Biggers <[email protected]>
Cc: Ingo Molnar <[email protected]>
Cc: Marco Elver <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Cc: Will Deacon <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts.py')
0 files changed, 0 insertions, 0 deletions