mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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
Date: Sun, 1 Aug 2004 21:02:41 +0200	[thread overview]
Message-ID: <20040801190241.GC2746@fs.tum.de> (raw)
In-Reply-To: <20040730083040.A2703153@wobbly.melbourne.sgi.com>

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



  reply	other threads:[~2004-08-01 19:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-20 11:44 4K stack kernel get Oops in Filesystem stress test Cahya Wirawan
2004-07-20 12:04 ` Steve Lord
2004-07-20 14:39   ` Jeffrey E. Hundstad
2004-07-20 19:50     ` [2.6 patch] let 4KSTACKS depend on EXPERIMENTAL and XFS on 4KSTACKS=n Adrian Bunk
2004-07-20 20:42       ` Chris Wedgwood
2004-07-20 20:50         ` Adrian Bunk
2004-07-20 20:58           ` Chris Wedgwood
2004-07-29  6:09       ` Nathan Scott
2004-07-29 11:42         ` Adrian Bunk
2004-07-29 11:46           ` Arjan van de Ven
2004-07-29 21:11             ` Adrian Bunk
2004-07-29 21:44               ` Chris Wedgwood
2004-07-29 22:30           ` [xfs-masters] " Nathan Scott
2004-08-01 19:02             ` Adrian Bunk [this message]
2004-07-29 15:42         ` Mika Bostrom
2004-07-29 16:09           ` Zwane Mwaikambo
2004-07-29 16:36             ` [2.6 patch] let 4KSTACKS depend on EXPERIMENTAL and XFS on 4KSTACKS Mika Bostrom
2004-07-22  7:27     ` 4K stack kernel get Oops in Filesystem stress test Amon Ott
2004-07-29  2:14       ` Nathan Scott

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=20040801190241.GC2746@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=akpm@osdl.org \
    --cc=arjanv@redhat.com \
    --cc=cwirawan@email.archlab.tuwien.ac.at \
    --cc=jeffrey.hundstad@mnsu.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@oss.sgi.com \
    --cc=lord@xfs.org \
    --cc=nathans@sgi.com \
    --cc=torvalds@osdl.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

Powered by JetHome