kmsan: compiler_types: declare __no_sanitize_or_inline
authorAlexander Potapenko <glider@google.com>
Fri, 26 Apr 2024 09:16:22 +0000 (11:16 +0200)
committerAndrew Morton <akpm@linux-foundation.org>
Mon, 6 May 2024 00:28:06 +0000 (17:28 -0700)
commit90d1f14cbb9ddbfc532e2da13bf6e0ed8320e792
treedd78f792e9b5651b73387d6ccbdf1486df8a6846
parent2aaba39e783a10fd1368626bce6f618a6a2a78b0
kmsan: compiler_types: declare __no_sanitize_or_inline

It turned out that KMSAN instruments READ_ONCE_NOCHECK(), resulting in
false positive reports, because __no_sanitize_or_inline enforced inlining.

Properly declare __no_sanitize_or_inline under __SANITIZE_MEMORY__, so
that it does not __always_inline the annotated function.

Link: https://lkml.kernel.org/r/20240426091622.3846771-1-glider@google.com
Fixes: 5de0ce85f5a4 ("kmsan: mark noinstr as __no_sanitize_memory")
Signed-off-by: Alexander Potapenko <glider@google.com>
Reported-by: syzbot+355c5bb8c1445c871ee8@syzkaller.appspotmail.com
Link: https://lkml.kernel.org/r/000000000000826ac1061675b0e3@google.com
Cc: <stable@vger.kernel.org>
Reviewed-by: Marco Elver <elver@google.com>
Cc: Dmitry Vyukov <dvyukov@google.com>
Cc: Miguel Ojeda <ojeda@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
include/linux/compiler_types.h