linux-kernel - [RFC PATCH] x86_64: double the x86

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1386743332-32171-1-git-send-email-yizhouzhou@ict.ac.cn>
Date:	Wed, 11 Dec 2013 14:28:52 +0800
From:	Zhouyi Zhou <zhouzhouyi@...il.com>
To:	linux-kernel@...r.kernel.org, <tglx@...utronix.de>,
	<mingo@...hat.com>, <hpa@...or.com>, <x86@...nel.org>,
	<bp@...en8.de>, <keescook@...omium.org>,
	<zhangyanfei@...fujitsu.com>
Cc:	Zhouyi Zhou <yizhouzhou@....ac.cn>
Subject: [RFC PATCH] x86_64: double the x86_64 kernel stack size?

Somethings I compiled the Linux network modules (especially bridge and netfilter)
without optimization, the kernel always crashes because of exhausted kernel stack.

The similar problem has been discussed in
http://lists.linuxfoundation.org/pipermail/bridge/2005-January/004402.html

Is it OK the double the x86_64 kernel stack size?
 

Signed-off-by: Zhouyi Zhou <yizhouzhou@....ac.cn>
Tested-by: Zhouyi Zhou  <yizhouzhou@....ac.cn>
---
 arch/x86/include/asm/page_64_types.h |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/x86/include/asm/page_64_types.h b/arch/x86/include/asm/page_64_types.h
index 43dcd80..dc4c629 100644
--- a/arch/x86/include/asm/page_64_types.h
+++ b/arch/x86/include/asm/page_64_types.h
@@ -1,7 +1,7 @@
 #ifndef _ASM_X86_PAGE_64_DEFS_H
 #define _ASM_X86_PAGE_64_DEFS_H
 
-#define THREAD_SIZE_ORDER	1
+#define THREAD_SIZE_ORDER	2
 #define THREAD_SIZE  (PAGE_SIZE << THREAD_SIZE_ORDER)
 #define CURRENT_MASK (~(THREAD_SIZE - 1))
 
-- 
1.7.10.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/