From: Nathan Scott <nathans@sgi.com>
To: Arjan van de Ven <arjanv@redhat.com>, Adrian Bunk <bunk@fs.tum.de>
Cc: "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: Re: [xfs-masters] Re: [2.6 patch] let 4KSTACKS depend on EXPERIMENTAL and XFS on 4KSTACKS=n
Date: Fri, 30 Jul 2004 08:30:40 +1000 [thread overview]
Message-ID: <20040730083040.A2703153@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <20040729114219.GN2349@fs.tum.de>; from bunk@fs.tum.de on Thu, Jul 29, 2004 at 01:42:19PM +0200
Arjan wrote:
> can you then also mark XFS broken in 2.4 entirely?
> 2.4 has a nett stack of also 4Kb...
The assumptions there are incorrect - 2.4 is now quite a
different kernel - we haven't seen problems like this on
2.4 at all, and I routinely test that failing code path
in our regression tests every other night on 2.4. There
have certainly been stack consumers in the 2.6 VFS that
weren't there in 2.4 (like AIO and struct kiocb, etc) so
thats not an apples-to-apples comparison anymore.
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.
cheers.
--
Nathan
next prev parent reply other threads:[~2004-07-29 22:36 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 ` Nathan Scott [this message]
2004-08-01 19:02 ` [2.6 patch] let 4KSTACKS depend on EXPERIMENTAL Adrian Bunk
2004-07-29 15:42 ` [2.6 patch] let 4KSTACKS depend on EXPERIMENTAL and XFS on 4KSTACKS=n 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=20040730083040.A2703153@wobbly.melbourne.sgi.com \
--to=nathans@sgi.com \
--cc=akpm@osdl.org \
--cc=arjanv@redhat.com \
--cc=bunk@fs.tum.de \
--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=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
all inboxes | Powered by JetHome®