linux-kernel - Re: mm/kmsan/instrumentation.c:41:26: warning: no previous prototype for function '__msan_metadata_ptr_for_load

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]

Message-ID: <953dda90-5a73-01f0-e5b7-2607e67dec13@suse.cz>
Date:   Wed, 11 Jan 2023 15:29:29 +0100
From:   Vlastimil Babka <vbabka@...e.cz>
To:     Alexander Potapenko <glider@...gle.com>
Cc:     kernel test robot <lkp@...el.com>, llvm@...ts.linux.dev,
        oe-kbuild-all@...ts.linux.dev, linux-kernel@...r.kernel.org,
        Christoph Lameter <cl@...ux-foundation.org>,
        Marco Elver <elver@...gle.com>,
        Dmitry Vyukov <dvyukov@...gle.com>,
        kasan-dev <kasan-dev@...glegroups.com>
Subject: Re: mm/kmsan/instrumentation.c:41:26: warning: no previous prototype
 for function '__msan_metadata_ptr_for_load_n'

On 1/11/23 13:10, Alexander Potapenko wrote:
> On Mon, Jan 2, 2023 at 11:01 AM Vlastimil Babka <vbabka@...e.cz> wrote:
>>
>> +CC kmsan folks.
>>
>> I think it's another side-effect where CONFIG_SLUB_TINY excludes KASAN which
>> in turn allows KMSAN to be enabled and uncover a pre-existing issue.
> 
>  Thanks for bringing this up, I'll fix this as Marco proposes.
> 
> Would it also make sense to exclude KMSAN with CONFIG_SLUB_TINY?

If the root causes are fixed, then it's not necessary? AFAIK SLUB_TINY only
indirectly caused KMSAN to be newly enabled in some configs, but there's no
fundamental incompatibility that I know of.