From: Hui Su <sh_def@163.com>
To: glider@google.com, elver@google.com, dvyukov@google.com,
catalin.marinas@arm.com, will@kernel.org,
kasan-dev@googlegroups.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: sh_def@163.com, sfr@canb.auug.org.au
Subject: [PATCH][next] arm64: fix the mm build error in mm/kfence/core.c
Date: Sun, 6 Dec 2020 01:22:07 +0800 [thread overview]
Message-ID: <20201205172207.GA4097@rlk> (raw)
When I build kernel with ARCH=arm64, the building errors came out like
this:
CC mm/kfence/core.o
In file included from ../mm/kfence/core.c:21:
../arch/arm64/include/asm/kfence.h: In function ‘kfence_protect_page’:
../arch/arm64/include/asm/kfence.h:12:2: error: implicit declaration of
function ‘set_memory_valid’ [-Werror=implicit-function-declaration]
12 | set_memory_valid(addr, 1, !protect);
| ^~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
which introduced by commit d54febeba2ff ("kfence: use pt_regs to
generate stack trace on faults").
Signed-off-by: Hui Su <sh_def@163.com>
---
arch/arm64/include/asm/kfence.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/include/asm/kfence.h b/arch/arm64/include/asm/kfence.h
index 6c0afeeab635..4d73e34da59d 100644
--- a/arch/arm64/include/asm/kfence.h
+++ b/arch/arm64/include/asm/kfence.h
@@ -4,6 +4,7 @@
#define __ASM_KFENCE_H
#include <asm/cacheflush.h>
+#include <linux/set_memory.h>
static inline bool arch_kfence_init_pool(void) { return true; }
--
2.25.1
next reply other threads:[~2020-12-05 18:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-05 17:22 Hui Su [this message]
2020-12-06 21:23 ` [PATCH][next] arm64: fix the mm build error in mm/kfence/core.c Stephen Rothwell
2020-12-06 22:08 ` Marco Elver
2020-12-07 14:52 ` Marco Elver
2020-12-07 20:32 ` Stephen Rothwell
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=20201205172207.GA4097@rlk \
--to=sh_def@163.com \
--cc=catalin.marinas@arm.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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).