From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Andrew Morton <akpm@linux-foundation.org>,
Yongqiang Liu <liuyongqiang13@huawei.com>,
Andrey Ryabinin <ryabinin.a.a@gmail.com>,
Dmitry Vyukov <dvyukov@google.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
Alexander Potapenko <glider@google.com>
Subject: Re: [next] kasan: shadow.c:528:33: error: 'VM_DELAY_KMEMLEAK' undeclared
Date: Thu, 25 Nov 2021 15:34:06 +0800 [thread overview]
Message-ID: <4d951721-caa2-f692-293d-ee8b93e62597@huawei.com> (raw)
In-Reply-To: <CA+G9fYuLv7491Q2AHcaUAQ2AQeFBQgx8w0DzK95Qf6Fh9gGFfQ@mail.gmail.com>
Sorry for the missing change of VM_DEFER_KMEMLEAK.
I will add Fixes tag and resend v4.
On 2021/11/25 15:13, Naresh Kamboju wrote:
> [ Please ignore this email if it is already reported ]
>
> While building Linux next 20211125 x86 with CONFIG_KASAN=y gcc-11
> following warnings / errors noticed.
>
> mm/kasan/shadow.c: In function 'kasan_module_alloc':
> mm/kasan/shadow.c:528:33: error: 'VM_DELAY_KMEMLEAK' undeclared (first
> use in this function); did you mean 'VM_DEFER_KMEMLEAK'?
> 528 | if (vm->flags & VM_DELAY_KMEMLEAK)
> | ^~~~~~~~~~~~~~~~~
> | VM_DEFER_KMEMLEAK
> mm/kasan/shadow.c:528:33: note: each undeclared identifier is reported
> only once for each function it appears in
> make[3]: *** [scripts/Makefile.build:288: mm/kasan/shadow.o] Error 1
>
> Build config:
> https://builds.tuxbuild.com/21OjEyx87iCX9bqOwJrZdl1wFFj/config
>
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> meta data:
> -----------
> git describe: next-20211125
> git_repo: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next
> git_sha: f81e94e91878bded599cc60f2881cfd50991aeb9
> git_short_log: f81e94e91878 (\"Add linux-next specific files for 20211125\")
> target_arch: x86
> toolchain: gcc-11
>
> steps to reproduce:
> tuxmake --runtime podman --target-arch x86_64 --toolchain gcc-11
> --kconfig defconfig \
> --kconfig-add https://builds.tuxbuild.com/21OjEyx87iCX9bqOwJrZdl1wFFj/config
>
> https://builds.tuxbuild.com/21OjEyx87iCX9bqOwJrZdl1wFFj/tuxmake_reproducer.sh
>
> --
> Linaro LKFT
> https://lkft.linaro.org
> .
next prev parent reply other threads:[~2021-11-25 7:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 7:13 Naresh Kamboju
2021-11-25 7:34 ` Kefeng Wang [this message]
2021-11-26 5:06 ` Stephen Rothwell
2021-11-25 7:53 ` Stephen Rothwell
2021-11-25 8:04 ` Kefeng Wang
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=4d951721-caa2-f692-293d-ee8b93e62597@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=borntraeger@linux.ibm.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=dave.hansen@linux.intel.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=liuyongqiang13@huawei.com \
--cc=mingo@redhat.com \
--cc=naresh.kamboju@linaro.org \
--cc=ryabinin.a.a@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
/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