From: Johannes Weiner <hannes@cmpxchg.org>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [patch rfc] memcg: correctly order reading PCG_USED and pc->mem_cgroup
Date: Thu, 20 Jan 2011 11:49:47 +0100 [thread overview]
Message-ID: <20110120104947.GK2232@cmpxchg.org> (raw)
In-Reply-To: <20110120100654.a90d9cc6.kamezawa.hiroyu@jp.fujitsu.com>
On Thu, Jan 20, 2011 at 10:06:54AM +0900, KAMEZAWA Hiroyuki wrote:
> On Wed, 19 Jan 2011 13:03:19 +0100
> Johannes Weiner <hannes@cmpxchg.org> wrote:
>
> > The placement of the read-side barrier is confused: the writer first
> > sets pc->mem_cgroup, then PCG_USED. The read-side barrier has to be
> > between testing PCG_USED and reading pc->mem_cgroup.
> >
> > Signed-off-by: Johannes Weiner <hannes@cmpxchg.org>
> > ---
> > mm/memcontrol.c | 27 +++++++++------------------
> > 1 files changed, 9 insertions(+), 18 deletions(-)
> >
> > I am a bit dumbfounded as to why this has never had any impact. I see
> > two scenarios where charging can race with LRU operations:
> >
> > One is shmem pages on swapoff. They are on the LRU when charged as
> > page cache, which could race with isolation/putback. This seems
> > sufficiently rare.
> >
> > The other case is a swap cache page being charged while somebody else
> > had it isolated. mem_cgroup_lru_del_before_commit_swapcache() would
> > see the page isolated and skip it. The commit then has to race with
> > putback, which could see PCG_USED but not pc->mem_cgroup, and crash
> > with a NULL pointer dereference. This does sound a bit more likely.
> >
> > Any idea? Am I missing something?
> >
>
> I think troubles happen only when PCG_USED bit was found but pc->mem_cgroup
> is NULL. Hmm.
Correct. Well, or get linked to the wrong LRU list and subsequently
prevent removal of both cgroups because it's impossible to empty them.
> set pc->mem_cgroup
> write_barrier
> set USED bit.
>
> read_barrier
> check USED bit
> access pc->mem_cgroup
>
> So, is there a case which only USED bit can be seen ?
That's what I am not quite sure about. As said, I think it can happen
when swap cache charging races with reclaim or migration.
When the two loads of the used bit and the memcg pointer get
reordered, it could observe a set PCG_USED and a stale/unset
pc->mem_cgroup.
For example:
swap minor fault: vmscan:
lookup_swap_cache()
unlock_page()
lock_page()
mem_cgroup_try_charge_swapin()
putback_lru_page()
mem_cgroup_add_lru_list()
p = pc->mem_cgroup
pc->mem_cgroup = FOO
smp_wmb()
pc->flags |= PCG_USED
f = pc->flags
if (!(f & PCG_USED))
return
*p /* bang */
> Anyway, your patch is right.
>
> Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Thank you.
Hannes
--
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 policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-01-20 10:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 12:03 Johannes Weiner
2011-01-20 1:06 ` KAMEZAWA Hiroyuki
2011-01-20 10:49 ` Johannes Weiner [this message]
2011-01-20 1:52 ` 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=20110120104947.GK2232@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nishimura@mxp.nes.nec.co.jp \
/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