bug for stack ?

bug for stack ?

[gaoqiang]

memory allocated for process stack seems never to be freed by the kernel..


on a vmware machine with about 768m memory, run the following program.when
printing "run over", run another case of the following program. oom-killer
trigered, which is not so reasonable.


#include <stdio.h>
#include <sys/time.h>
#include <sys/resource.h>
#include <alloca.h>
void*stack=NULL;
const long water_mark=512*1024*1024;
void func()
{
	int p=0;
	if((long)stack-(long)&p> water_mark)
	{
		printf("hit\n");
	}
	else
	{
		func();
	}
	return;
}
int main()
{
	struct rlimit limit;
	limit.rlim_cur=1024*1024*1024*1.5;
	limit.rlim_max=1024*1024*1024*1.5;
	setrlimit(RLIMIT_STACK,&limit);
	int a=0;
	stack=&a;
	printf("run\n");
	//getchar();
	func();
	printf("run over\n");
	getchar();
	return 0;
}

-- 
使用 Opera 革命性的电子邮件客户程序: http://www.opera.com/mail/

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

Re: bug for stack ?

[Rik van Riel]

On 04/17/2012 05:20 AM, gaoqiang wrote:
>
> memory allocated for process stack seems never to be freed by the kernel..

It should get freed on process exit.

> on a vmware machine with about 768m memory, run the following program.when
> printing "run over", run another case of the following program. oom-killer
> trigered, which is not so reasonable.

You start your second run before your first run
has exited.  The system does not have enough
memory for two such runs, so you run out of
memory.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>