From: "H. Peter Anvin" <hpa@zytor.com>
To: Zhouyi Zhou <zhouzhouyi@gmail.com>,
linux-kernel@vger.kernel.org, tglx@linutronix.de,
mingo@redhat.com, x86@kernel.org, bp@alien8.de,
keescook@chromium.org, zhangyanfei@cn.fujitsu.com
Cc: Zhouyi Zhou <yizhouzhou@ict.ac.cn>
Subject: Re: [RFC PATCH] x86_64: double the x86_64 kernel stack size?
Date: Wed, 11 Dec 2013 12:29:57 -0800 [thread overview]
Message-ID: <52A8CB45.2080704@zytor.com> (raw)
In-Reply-To: <1386743332-32171-1-git-send-email-yizhouzhou@ict.ac.cn>
On 12/10/2013 10:28 PM, Zhouyi Zhou wrote:
> 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?
>
Hell no.
-hpa
prev parent reply other threads:[~2013-12-11 20:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 6:28 [RFC PATCH] x86_64: double the x86_64 kernel stack size? Zhouyi Zhou
2013-12-11 20:29 ` H. Peter Anvin [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=52A8CB45.2080704@zytor.com \
--to=hpa@zytor.com \
--cc=bp@alien8.de \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yizhouzhou@ict.ac.cn \
--cc=zhangyanfei@cn.fujitsu.com \
--cc=zhouzhouyi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.