From: Adrian Bunk <bunk@fs.tum.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: [2.6 patch] let 4KSTACKS depend on EXPERIMENTAL (fwd)
Date: Tue, 3 Aug 2004 00:59:52 +0200 [thread overview]
Message-ID: <20040802225951.GR2746@fs.tum.de> (raw)
Hi Andrew,
I'd like to see the patch below included in 2.6.8 .
----- Forwarded message from Adrian Bunk <bunk@fs.tum.de> -----
Date: Sun, 1 Aug 2004 21:02:41 +0200
From: Adrian Bunk <bunk@fs.tum.de>
To: Nathan Scott <nathans@sgi.com>
Cc: Arjan van de Ven <arjanv@redhat.com>,
"Jeffrey E. Hundstad" <jeffrey.hundstad@mnsu.edu>,
Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
Steve Lord <lord@xfs.org>, linux-xfs@oss.sgi.com,
Cahya Wirawan <cwirawan@email.archlab.tuwien.ac.at>,
linux-kernel@vger.kernel.org
Subject: [2.6 patch] let 4KSTACKS depend on EXPERIMENTAL
On Fri, Jul 30, 2004 at 08:30:40AM +1000, Nathan Scott wrote:
>...
> Adrian wrote:
> > 2.6 is a stable kernel series used in production environments.
> >
> > Regarding Linus' tree, it's IMHO the best solution to work around it
> > this way until all issues are sorted out.
>
> I'm not really convinced - the EXPERIMENTAL marking should
> be plenty of a deterent to folks in production environments.
> There are reports of stack overruns on other filesystems as
> well with 4KSTACKS, so doesn't seem worthwhile to me to do
> this just for XFS.
OK, below is a patch that only adds a dependency of 4KSTACKS on
EXPERIMENTAL.
Considering that not all issues with 4kb stacks are currently corrected,
this patch should IMHO go in 2.6.8 .
Signed-off-by: Adrian Bunk <bunk@fs.tum.de>
--- linux-2.6.8-rc2-mm1-full/arch/i386/Kconfig.old 2004-08-01 20:59:02.000000000 +0200
+++ linux-2.6.8-rc2-mm1-full/arch/i386/Kconfig 2004-08-01 20:59:46.000000000 +0200
@@ -1474,7 +1474,8 @@
to solve problems without frame pointers.
config 4KSTACKS
- bool "Use 4Kb for kernel stacks instead of 8Kb"
+ bool "Use 4Kb for kernel stacks instead of 8Kb (EXPERIMENTAL)"
+ depends on EXPERIMENTAL
help
If you say Y here the kernel will use a 4Kb stacksize for the
kernel stack attached to each process/thread. This facilitates
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
----- End forwarded message -----
next reply other threads:[~2004-08-02 23:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 22:59 Adrian Bunk [this message]
2004-08-02 23:28 ` [2.6 patch] let 4KSTACKS depend on EXPERIMENTAL (fwd) Andrew Morton
2004-08-03 0:45 ` Adrian Bunk
2004-08-02 23:56 ` Alan Cox
2004-08-03 13:13 ` Adrian Bunk
2004-08-03 13:26 ` Dave Jones
2004-08-03 20:11 ` Adrian Bunk
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=20040802225951.GR2746@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.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