From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: 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>,
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: Fri, 26 Nov 2021 16:06:51 +1100 [thread overview]
Message-ID: <20211126160651.318875c3@canb.auug.org.au> (raw)
In-Reply-To: <4d951721-caa2-f692-293d-ee8b93e62597@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 1009 bytes --]
Hi all,
On Thu, 25 Nov 2021 15:34:06 +0800 Kefeng Wang <wangkefeng.wang@huawei.com> wrote:
>
> Sorry for the missing change of VM_DEFER_KMEMLEAK.
>
> I will add Fixes tag and resend v4.
I have applied the following patch to linux-next today:
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Fri, 26 Nov 2021 15:34:11 +1100
Subject: [PATCH] mm: kasan: fix VM_DELAY_KMEMLEAK typo
Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
mm/kasan/shadow.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/kasan/shadow.c b/mm/kasan/shadow.c
index 2ade2f484562..94136f84b449 100644
--- a/mm/kasan/shadow.c
+++ b/mm/kasan/shadow.c
@@ -525,7 +525,7 @@ int kasan_module_alloc(void *addr, size_t size, gfp_t gfp_mask)
vm->flags |= VM_KASAN;
kmemleak_ignore(ret);
- if (vm->flags & VM_DELAY_KMEMLEAK)
+ if (vm->flags & VM_DEFER_KMEMLEAK)
kmemleak_vmalloc(vm, size, gfp_mask);
return 0;
--
2.33.0
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-11-26 5:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 7:13 [next] kasan: shadow.c:528:33: error: 'VM_DELAY_KMEMLEAK' undeclared Naresh Kamboju
2021-11-25 7:34 ` Kefeng Wang
2021-11-26 5:06 ` Stephen Rothwell [this message]
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=20211126160651.318875c3@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--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=tglx@linutronix.de \
--cc=wangkefeng.wang@huawei.com \
--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;
as well as URLs for NNTP newsgroup(s).