linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: nishimura@mxp.nes.nec.co.jp,
	Daisuke Nishimura <d-nishimura@mtf.biglobe.ne.jp>,
	linux-mm <linux-mm@kvack.org>,
	Balbir Singh <balbir@linux.vnet.ibm.com>,
	Hugh Dickins <hugh@veritas.com>
Subject: Re: [PATCH] fix unused/stale swap cache handling on memcg  v3
Date: Tue, 21 Apr 2009 13:05:49 +0900	[thread overview]
Message-ID: <20090421130549.72cd1d6a.nishimura@mxp.nes.nec.co.jp> (raw)
In-Reply-To: <20090421115749.bcb12fa7.kamezawa.hiroyu@jp.fujitsu.com>

On Tue, 21 Apr 2009 11:57:49 +0900, KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> On Tue, 21 Apr 2009 11:35:25 +0900
> Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp> wrote:
> 
> > @@ -785,6 +786,23 @@ activate_locked:
> >                 SetPageActive(page);
> >                 pgactivate++;
> >  keep_locked:
> > +               if (!scanning_global_lru(sc) && PageSwapCache(page)) {
> > +                       struct page_cgroup *pc;
> > +
> > +                       pc = lookup_page_cgroup(page);
> > +                       /*
> > +                        * Used bit of swapcache is solid under page lock.
> > +                        */
> > +                       if (unlikely(!PageCgroupUsed(pc)))
> > +                               /*
> > +                                * This can happen if the page is free'ed by
> > +                                * the owner process before it is added to
> > +                                * swapcache.
> > +                                * These swapcache cannot be managed by memcg
> > +                                * well, so free it here.
> > +                                */
> > +                               try_to_free_swap(page);
> > +               }
> >                 unlock_page(page);
> >  keep:
> >                 list_add(&page->lru, &ret_pages);
> > 
> > This cannot prevent type-1 orphan SwapCache(caused by the race
> > between exit() and swap-in readahead).
> > Type-1 can pressure the memsw usage(trigger OOM if memsw.limit is set, as a result)
> > and make struct mem_cgroup unfreeable even after rmdir(because it holds refcount
> > to mem_cgroup).
> Hmm.
>    free_swap_cache()
> 	-> trylock_page() => failure case ?
> 
Yes, but there is another case:

            processA                   |           processB
  -------------------------------------+-------------------------------------
    (free_swap_and_cache())            |  (read_swap_cache_async())
                                       |    swap_duplicate()
      swap_entry_free() == 1           |
      find_get_page() -> cannot find   |
                                       |    __set_page_locked()
                                       |    add_to_swap_cache()
                                       |    lru_cache_add_anon()
                                       |      doesn't link this page to memcg's
                                       |      LRU, because of !PageCgroupUsed.


> add following codes.
> ==
>  588                         page = find_get_page(&swapper_space, entry.val);
>  589                         if (page && !trylock_page(page)) {
> 				     mem_cgroup_retry_free_swap_lazy(page);  <=====
>  590                                 page_cache_release(page);
>  591                                 page = NULL;
>  592                         }
> ==
> and  do some kind of lazy ops..I'll try some.
> 
> > 
> > Do you have any ideas to solve orphan SwapCache problem by adding some hooks to shrink_zone() ?
> > (scan some pages from global LRU and check whether it's orphan SwapCache or not by
> > adding some code like above ?)
> > 
> > And, what do you think about adding above code to shrink_page_list() ?
> > I think it might be unnecessary if we can solve the problem in another way, though.
> > 
> 
> I think your hook itself is not very bad. (even if we remove this later..)
> 
I think it depends on how we fix the type-1 whether we should remove this or not.
Anyway, I'll leave it as it is for now.


Thanks,
Daisuke Nishimura.

--
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>

  reply	other threads:[~2009-04-21  4:09 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-17  4:57 [RFC] memcg: handle swapcache leak Daisuke Nishimura
2009-03-17  5:39 ` KAMEZAWA Hiroyuki
2009-03-17  6:11   ` Daisuke Nishimura
2009-03-17  7:29     ` KAMEZAWA Hiroyuki
2009-03-17  9:38       ` KAMEZAWA Hiroyuki
2009-03-18  1:17         ` Daisuke Nishimura
2009-03-18  1:34           ` KAMEZAWA Hiroyuki
2009-03-18  3:51             ` Daisuke Nishimura
2009-03-18  4:05               ` KAMEZAWA Hiroyuki
2009-03-18  8:57               ` [PATCH] fix unused/stale swap cache handling on memcg v1 (Re: " KAMEZAWA Hiroyuki
2009-03-18 14:17                 ` Daisuke Nishimura
2009-03-18 23:45                   ` KAMEZAWA Hiroyuki
2009-03-19  2:16                     ` KAMEZAWA Hiroyuki
2009-03-19  9:06                       ` [PATCH] fix unused/stale swap cache handling on memcg v2 KAMEZAWA Hiroyuki
2009-03-19 10:01                         ` Daisuke Nishimura
2009-03-19 10:13                           ` Daisuke Nishimura
2009-03-19 10:46                             ` KAMEZAWA Hiroyuki
2009-03-19 11:36                               ` KAMEZAWA Hiroyuki
2009-03-20  7:45                                 ` [PATCH] fix unused/stale swap cache handling on memcg v3 KAMEZAWA Hiroyuki
2009-03-23  1:45                                   ` Daisuke Nishimura
2009-03-23  2:41                                     ` KAMEZAWA Hiroyuki
2009-03-23  5:04                                       ` Daisuke Nishimura
2009-03-23  5:22                                         ` KAMEZAWA Hiroyuki
2009-03-24  8:32                                           ` Daisuke Nishimura
2009-03-24 23:57                                             ` KAMEZAWA Hiroyuki
2009-04-17  6:34                                               ` Daisuke Nishimura
2009-04-17  6:54                                                 ` KAMEZAWA Hiroyuki
2009-04-17  7:50                                                   ` Daisuke Nishimura
2009-04-17  7:58                                                     ` KAMEZAWA Hiroyuki
2009-04-17  8:12                                                       ` Daisuke Nishimura
2009-04-17  8:13                                                         ` KAMEZAWA Hiroyuki
2009-04-21  2:35                                                           ` Daisuke Nishimura
2009-04-21  2:57                                                             ` KAMEZAWA Hiroyuki
2009-04-21  4:05                                                               ` Daisuke Nishimura [this message]
2009-04-17  8:11                                                     ` KAMEZAWA Hiroyuki
2009-03-18  0:08       ` [RFC] memcg: handle swapcache leak Daisuke Nishimura

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=20090421130549.72cd1d6a.nishimura@mxp.nes.nec.co.jp \
    --to=nishimura@mxp.nes.nec.co.jp \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=d-nishimura@mtf.biglobe.ne.jp \
    --cc=hugh@veritas.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-mm@kvack.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