From: zhongjiang <zhongjiang@huawei.com>
To: linux-kernel@vger.kernel.org, ryabinin.a.a@gmail.com,
linux-mm@kvack.org, catalin.marinas@arm.com,
akpm@linux-foundation.org
Cc: qiuxishi@huawei.com, zhongjiang@huawei.com, long.wanglong@huawei.com
Subject: [PATCH] arm64: fix add kasan bug
Date: Thu, 31 Dec 2015 18:09:09 +0800 [thread overview]
Message-ID: <1451556549-8962-1-git-send-email-zhongjiang@huawei.com> (raw)
From: zhong jiang <zhongjiang@huawei.com>
In general, each process have 16kb stack space to use, but
stack need extra space to store red_zone when kasan enable.
the patch fix above question.
Signed-off-by: zhong jiang <zhongjiang@huawei.com>
---
arch/arm64/include/asm/thread_info.h | 15 +++++++++++++--
1 file changed, 13 insertions(+), 2 deletions(-)
diff --git a/arch/arm64/include/asm/thread_info.h b/arch/arm64/include/asm/thread_info.h
index 90c7ff2..45b5a7e 100644
--- a/arch/arm64/include/asm/thread_info.h
+++ b/arch/arm64/include/asm/thread_info.h
@@ -23,13 +23,24 @@
#include <linux/compiler.h>
+#ifdef CONFIG_KASAN
+#define KASAN_STACK_ORDER 1
+#else
+#define KASAN_STACK_ORDER 0
+#endif
+
#ifdef CONFIG_ARM64_4K_PAGES
-#define THREAD_SIZE_ORDER 2
+#define THREAD_SIZE_ORDER (2 + KASAN_STACK_ORDER)
#elif defined(CONFIG_ARM64_16K_PAGES)
-#define THREAD_SIZE_ORDER 0
+#define THREAD_SIZE_ORDER (0 + KASAN_STACK_ORDER)
#endif
+#ifdef CONFIG_KASAN
+#define THREAD_SIZE 32768
+#else
#define THREAD_SIZE 16384
+#endif
+
#define THREAD_START_SP (THREAD_SIZE - 16)
#ifndef __ASSEMBLY__
--
2.0.0
--
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>
next reply other threads:[~2015-12-31 10:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-31 10:09 zhongjiang [this message]
2016-01-04 21:13 ` Andrew Morton
2016-01-05 10:13 ` Catalin Marinas
2016-01-05 10:10 ` Catalin Marinas
2016-01-05 21:17 ` Andrey Ryabinin
2016-01-08 18:27 ` Catalin Marinas
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=1451556549-8962-1-git-send-email-zhongjiang@huawei.com \
--to=zhongjiang@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=long.wanglong@huawei.com \
--cc=qiuxishi@huawei.com \
--cc=ryabinin.a.a@gmail.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