From: kbuild test robot <fengguang.wu@intel.com>
To: Alexander Potapenko <glider@google.com>
Cc: kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
Greg Hackmann <ghackmann@google.com>,
Paul Lawrence <paullawrence@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [RFC PATCH mmotm] kasan: __asan_set_shadow_00 can be static
Date: Sat, 23 Dec 2017 20:59:43 +0800 [thread overview]
Message-ID: <20171223125943.GA74341@lkp-ib03> (raw)
In-Reply-To: <201712232039.vNkPEjbE%fengguang.wu@intel.com>
Fixes: 1749be8333b7 ("kasan: add functions for unpoisoning stack variables")
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
kasan.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/mm/kasan/kasan.c b/mm/kasan/kasan.c
index 8aaee42..dcfcb26 100644
--- a/mm/kasan/kasan.c
+++ b/mm/kasan/kasan.c
@@ -778,12 +778,12 @@ EXPORT_SYMBOL(__asan_allocas_unpoison);
} \
EXPORT_SYMBOL(__asan_set_shadow_##byte)
-DEFINE_ASAN_SET_SHADOW(00);
-DEFINE_ASAN_SET_SHADOW(f1);
-DEFINE_ASAN_SET_SHADOW(f2);
-DEFINE_ASAN_SET_SHADOW(f3);
-DEFINE_ASAN_SET_SHADOW(f5);
-DEFINE_ASAN_SET_SHADOW(f8);
+static DEFINE_ASAN_SET_SHADOW(00);
+static DEFINE_ASAN_SET_SHADOW(f1);
+static DEFINE_ASAN_SET_SHADOW(f2);
+static DEFINE_ASAN_SET_SHADOW(f3);
+static DEFINE_ASAN_SET_SHADOW(f5);
+static DEFINE_ASAN_SET_SHADOW(f8);
#ifdef CONFIG_MEMORY_HOTPLUG
static int __meminit kasan_mem_notifier(struct notifier_block *nb,
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2017-12-23 12:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-23 12:59 [mmotm:master 157/234] mm/kasan/kasan.c:781:1: sparse: symbol '__asan_set_shadow_00' was not declared. Should it be static? kbuild test robot
2017-12-23 12:59 ` kbuild test robot [this message]
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=20171223125943.GA74341@lkp-ib03 \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=ghackmann@google.com \
--cc=glider@google.com \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=paullawrence@google.com \
/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