Re: [xfs-masters] Re: [2.6 patch] let 4KSTACKS depend on EXPERIMENTAL and XFS on 4KSTACKS=n

[Nathan Scott]

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/