linux-kernel - Re: [PATCH] kmsan: compiler_types: declare __no_sanitize_or

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Thu, 25 Apr 2024 13:31:21 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Alexander Potapenko <glider@...gle.com>
Cc: elver@...gle.com, dvyukov@...gle.com, ojeda@...nel.org,
 linux-kernel@...r.kernel.org,
 syzbot+355c5bb8c1445c871ee8@...kaller.appspotmail.com
Subject: Re: [PATCH] kmsan: compiler_types: declare __no_sanitize_or_inline

On Thu, 25 Apr 2024 11:28:59 +0200 Alexander Potapenko <glider@...gle.com> wrote:

> 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 inline the annotated function.
> 
> Reported-by: syzbot+355c5bb8c1445c871ee8@...kaller.appspotmail.com

I'll add

Link: https://lkml.kernel.org/r/000000000000826ac1061675b0e3@google.com

And I think a cc:stable is justifiable.  A Fixes: target would be nice?