From: Alexander Nyberg <alexn@dsv.su.se>
To: torvalds@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] Warn about dangers of LVM/RAID stacking with 4KSTACKS
Date: Fri, 10 Dec 2004 17:10:35 +0100 [thread overview]
Message-ID: <1102695035.690.11.camel@boxen> (raw)
Hello Linus
On x86 using software RAID on disks and then putting them together in
LVM as a logical volume uses alot of the stack. I've read reports of
doing this on volumes which are shared via NFS causes stack overruns
which it indeed does, I just reproduced it here.
We should play it safe and warn anyone before using CONFIG_4KSTACKS if
the user intends to do software LVM/RAID stacking until this issue is
resolved.
Signed-off-by: Alexander Nyberg <alexn@dsv.su.se>
===== arch/i386/Kconfig.debug 1.4 vs edited =====
--- 1.4/arch/i386/Kconfig.debug 2004-10-20 10:37:19 +02:00
+++ edited/arch/i386/Kconfig.debug 2004-12-10 17:00:01 +01:00
@@ -46,6 +46,8 @@ config DEBUG_PAGEALLOC
This results in a large slowdown, but helps to find certain types
of memory corruptions.
+comment "Please read help if you intend to stack software RAID and LVM"
+
config 4KSTACKS
bool "Use 4Kb for kernel stacks instead of 8Kb"
help
@@ -54,6 +56,10 @@ config 4KSTACKS
running more threads on a system and also reduces the pressure
on the VM subsystem for higher order allocations. This option
will also use IRQ stacks to compensate for the reduced stackspace.
+
+ Don't enable this if you intend to stack RAID and LVM on top of
+ each other. The stack may run out using this combination and
+ then bad things will happen.
config X86_FIND_SMP_CONFIG
bool
reply other threads:[~2004-12-10 16:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1102695035.690.11.camel@boxen \
--to=alexn@dsv.su.se \
--cc=linux-kernel@vger.kernel.org \
--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