From: Guenter Roeck <linux@roeck-us.net>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linux-kernel@vger.kernel.org, ul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org, Guenter Roeck <linux@roeck-us.net>,
Daniel Axtens <dja@axtens.net>
Subject: [PATCH] powerpc/prom_init: Add memset as valid external symbol if CONFIG_KASAN=y
Date: Sat, 18 Jun 2022 20:52:46 -0700 [thread overview]
Message-ID: <20220619035246.2633538-1-linux@roeck-us.net> (raw)
If CONFIG_KASAN=y, powerpc:allmodconfig fails to build with the following
error.
Error: External symbol 'memset' referenced from prom_init.c
The problem was introduced with commit 41b7a347bf14 ("powerpc: Book3S
64-bit outline-only KASAN support"). So far, with CONFIG_KASAN=y, only
__memset was accepted as valid external symbol in prom_init_check.sh.
Add memset as well to fix the problem.
Fixes: 41b7a347bf14 ("powerpc: Book3S 64-bit outline-only KASAN support")
Cc: Michael Ellerman <mpe@ellerman.id.au>
Cc: Daniel Axtens <dja@axtens.net>
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
---
arch/powerpc/kernel/prom_init_check.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/powerpc/kernel/prom_init_check.sh b/arch/powerpc/kernel/prom_init_check.sh
index b183ab9c5107..787142b5dd26 100644
--- a/arch/powerpc/kernel/prom_init_check.sh
+++ b/arch/powerpc/kernel/prom_init_check.sh
@@ -16,7 +16,7 @@
grep "^CONFIG_KASAN=y$" .config >/dev/null
if [ $? -eq 0 ]
then
- MEM_FUNCS="__memcpy __memset"
+ MEM_FUNCS="__memcpy __memset memset"
else
MEM_FUNCS="memcpy memset"
fi
--
2.35.1
next reply other threads:[~2022-06-19 3:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-19 3:52 Guenter Roeck [this message]
2022-06-19 6:45 ` [PATCH] powerpc/prom_init: Add memset as valid external symbol if CONFIG_KASAN=y Christophe Leroy
2022-06-19 6:55 ` Christophe Leroy
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=20220619035246.2633538-1-linux@roeck-us.net \
--to=linux@roeck-us.net \
--cc=dja@axtens.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.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