linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: nishimura@mxp.nes.nec.co.jp,
	Balbir Singh <balbir@linux.vnet.ibm.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [RFC] [PATCH] memcg: fix infinite loop
Date: Thu, 15 Jan 2009 15:16:57 +0900	[thread overview]
Message-ID: <20090115151657.84eb1a03.nishimura@mxp.nes.nec.co.jp> (raw)
In-Reply-To: <496ED2B7.5050902@cn.fujitsu.com>

On Thu, 15 Jan 2009 14:07:51 +0800, Li Zefan <lizf@cn.fujitsu.com> wrote:
> 1. task p1 is in /memcg/0
> 2. p1 does mmap(4096*2, MAP_LOCKED)
> 3. echo 4096 > /memcg/0/memory.limit_in_bytes
> 
> The above 'echo' will never return, unless p1 exited or freed the memory.
> The cause is we can't reclaim memory from p1, so the while loop in
> mem_cgroup_resize_limit() won't break.
> 
But it can be interrupted, right ?

I don't think this would be a big problem.


Thanks,
Daisuke Nishimura.

> This patch fixes it by decrementing retry_count regardless the return value
> of mem_cgroup_hierarchical_reclaim().
> 
> Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
> ---
>  mm/memcontrol.c |   15 ++++-----------
>  1 files changed, 4 insertions(+), 11 deletions(-)
> 
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index fb62b43..1995098 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -1524,11 +1524,10 @@ static int mem_cgroup_resize_limit(struct mem_cgroup *memcg,
>  {
>  
>  	int retry_count = MEM_CGROUP_RECLAIM_RETRIES;
> -	int progress;
>  	u64 memswlimit;
>  	int ret = 0;
>  
> -	while (retry_count) {
> +	while (retry_count--) {
>  		if (signal_pending(current)) {
>  			ret = -EINTR;
>  			break;
> @@ -1551,9 +1550,7 @@ static int mem_cgroup_resize_limit(struct mem_cgroup *memcg,
>  		if (!ret)
>  			break;
>  
> -		progress = mem_cgroup_hierarchical_reclaim(memcg, GFP_KERNEL,
> -							   false);
> -  		if (!progress)			retry_count--;
> +		mem_cgroup_hierarchical_reclaim(memcg, GFP_KERNEL, false);
>  	}
>  
>  	return ret;
> @@ -1563,13 +1560,13 @@ int mem_cgroup_resize_memsw_limit(struct mem_cgroup *memcg,
>  				unsigned long long val)
>  {
>  	int retry_count = MEM_CGROUP_RECLAIM_RETRIES;
> -	u64 memlimit, oldusage, curusage;
> +	u64 memlimit;
>  	int ret;
>  
>  	if (!do_swap_account)
>  		return -EINVAL;
>  
> -	while (retry_count) {
> +	while (retry_count--) {
>  		if (signal_pending(current)) {
>  			ret = -EINTR;
>  			break;
> @@ -1592,11 +1589,7 @@ int mem_cgroup_resize_memsw_limit(struct mem_cgroup *memcg,
>  		if (!ret)
>  			break;
>  
> -		oldusage = res_counter_read_u64(&memcg->memsw, RES_USAGE);
>  		mem_cgroup_hierarchical_reclaim(memcg, GFP_KERNEL, true);
> -		curusage = res_counter_read_u64(&memcg->memsw, RES_USAGE);
> -		if (curusage >= oldusage)
> -			retry_count--;
>  	}
>  	return ret;
>  }
> -- 
> 1.5.4.rc3
> 
> 

--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2009-01-15  6:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-15  6:07 Li Zefan
2009-01-15  6:15 ` Balbir Singh
2009-01-15  6:31   ` KAMEZAWA Hiroyuki
2009-01-15  7:14     ` Li Zefan
2009-01-15  7:21       ` KAMEZAWA Hiroyuki
2009-01-15  7:26         ` Balbir Singh
2009-01-15  7:32         ` Li Zefan
2009-01-15  7:35           ` KAMEZAWA Hiroyuki
2009-01-15  6:16 ` Daisuke Nishimura [this message]
2009-01-15  6:27   ` Li Zefan
2009-01-19  8:49 ` KAMEZAWA Hiroyuki
2009-01-19  9:57   ` Balbir Singh
2009-01-19 10:07     ` KAMEZAWA Hiroyuki

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=20090115151657.84eb1a03.nishimura@mxp.nes.nec.co.jp \
    --to=nishimura@mxp.nes.nec.co.jp \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=lizf@cn.fujitsu.com \
    /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