From: Vlastimil Babka <vbabka@suse.cz>
To: Alexander Potapenko <glider@google.com>
Cc: kernel test robot <lkp@intel.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org,
Christoph Lameter <cl@linux-foundation.org>,
Marco Elver <elver@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
kasan-dev <kasan-dev@googlegroups.com>
Subject: Re: mm/kmsan/instrumentation.c:41:26: warning: no previous prototype for function '__msan_metadata_ptr_for_load_n'
Date: Wed, 11 Jan 2023 15:29:29 +0100 [thread overview]
Message-ID: <953dda90-5a73-01f0-e5b7-2607e67dec13@suse.cz> (raw)
In-Reply-To: <CAG_fn=XmHKvpev4Gxv=SFOf2Kz0AwiuudXPqPjVJJo2gN=yOcg@mail.gmail.com>
On 1/11/23 13:10, Alexander Potapenko wrote:
> On Mon, Jan 2, 2023 at 11:01 AM Vlastimil Babka <vbabka@suse.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.
next prev parent reply other threads:[~2023-01-11 14:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-01 19:10 kernel test robot
2023-01-02 10:01 ` Vlastimil Babka
2023-01-02 10:27 ` Marco Elver
2023-01-11 12:10 ` Alexander Potapenko
2023-01-11 14:29 ` Vlastimil Babka [this message]
2023-01-12 9:15 ` Alexander Potapenko
2023-01-12 10:26 ` Alexander Potapenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=953dda90-5a73-01f0-e5b7-2607e67dec13@suse.cz \
--to=vbabka@suse.cz \
--cc=cl@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®