Re: restrict initial stack space expansion to rlimit - the processkiller...

From: PaweÅ Sikora
Date: Thu Mar 04 2010 - 08:26:50 EST

Dnia 04-03-2010 o 11:05:03 AmÃrico Wang <xiyou.wangcong@xxxxxxxxx> napisaÅ(a):

2010/3/4 PaweÅ Sikora <pawel.sikora@xxxxxxxx>:
Hi all,

i'm currently testing the and observing random process killing
on my builder machine (x86-64) which contains several tcl/bash
scripts for svn checkout, compilation, archive and ftp deploying.

here's a fragment of build log:

[CXX] obj-release-i486-gnu-linux/genMappingRst.o
[CXX] obj-release-i486-gnu-linux/otelloVerdiThread.o
i486-gnu-linux-g++: Internal error: Killed (program as)
Please submit a full bug report.
See <> for instructions.
make[1]: *** [obj-release-i486-gnu-linux/genMappingRst.o] Error 1

the builder process tree looks like this:

$ pstree -Acl
| `-cc1plus
| `-tee

as you can see there're few levels of bash and tclsh(8.4)
and make/ccache/binutils/g++ workers at the bottom.

i've noticed that rolling back to the (or just reverting
the 'ulimit -s' commit: 35e2093d5d7b632c083af3578c05876375828314)
fixes the problem.

so, is it my stack ulimit (8192) to small, or maybe the new limit
calculations are wrong? shoud i bump the stack limit for new kernels?

Please check if you have this patch:

Thanks! + a17e18790a8c47113a73139d54a375dc9ccd8f08 works fine.
i think it should be pushed to as soon as possible.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at