From: Michal Hocko <mhocko@suse.cz>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Ying Han <yinghan@google.com>, Tejun Heo <htejun@gmail.com>,
Glauber Costa <glommer@parallels.com>,
Li Zefan <lizefan@huawei.com>
Subject: Re: [PATCH v3 4/7] memcg: remove memcg from the reclaim iterators
Date: Tue, 12 Feb 2013 18:12:16 +0100 [thread overview]
Message-ID: <20130212171216.GA17663@dhcp22.suse.cz> (raw)
In-Reply-To: <63d3b5fa-dbc6-4bc9-8867-f9961e644305@email.android.com>
On Tue 12-02-13 11:41:03, Johannes Weiner wrote:
>
>
> Michal Hocko <mhocko@suse.cz> wrote:
>
> >On Tue 12-02-13 17:13:32, Michal Hocko wrote:
> >> On Tue 12-02-13 16:43:30, Michal Hocko wrote:
> >> [...]
> >> The example was not complete:
> >>
> >> > Wait a moment. But what prevents from the following race?
> >> >
> >> > rcu_read_lock()
> >>
> >> cgroup_next_descendant_pre
> >> css_tryget(css);
> >> memcg = mem_cgroup_from_css(css) atomic_add(CSS_DEACT_BIAS,
> >&css->refcnt)
> >>
> >> > mem_cgroup_css_offline(memcg)
> >>
> >> We should be safe if we did synchronize_rcu() before
> >root->dead_count++,
> >> no?
> >> Because then we would have a guarantee that if css_tryget(memcg)
> >> suceeded then we wouldn't race with dead_count++ it triggered.
> >>
> >> > root->dead_count++
> >> > iter->last_dead_count = root->dead_count
> >> > iter->last_visited = memcg
> >> > // final
> >> > css_put(memcg);
> >> > // last_visited is still valid
> >> > rcu_read_unlock()
> >> > [...]
> >> > // next iteration
> >> > rcu_read_lock()
> >> > iter->last_dead_count == root->dead_count
> >> > // KABOOM
> >
> >Ohh I have missed that we took a reference on the current memcg which
> >will be stored into last_visited. And then later, during the next
> >iteration it will be still alive until we are done because previous
> >patch moved css_put to the very end.
> >So this race is not possible. I still need to think about parallel
> >iteration and a race with removal.
>
> I thought the whole point was to not have a reference in last_visited
> because have the iterator might be unused indefinitely :-)
OK, it seems that I managed to confuse ;)
> We only store a pointer and validate it before use the next time
> around. So I think the race is still possible, but we can deal with
> it by not losing concurrent dead count changes, i.e. one atomic read
> in the iterator function.
All reads from root->dead_count are atomic already, so I am not sure
what you mean here. Anyway, I hope I won't make this even more confusing
if I post what I have right now:
---
next prev parent reply other threads:[~2013-02-12 17:12 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 17:54 [PATCH v3 0/7] rework mem_cgroup iterator Michal Hocko
2013-01-03 17:54 ` [PATCH v3 1/7] memcg: synchronize per-zone iterator access by a spinlock Michal Hocko
2013-01-03 17:54 ` [PATCH v3 2/7] memcg: keep prev's css alive for the whole mem_cgroup_iter Michal Hocko
2013-01-03 17:54 ` [PATCH v3 3/7] memcg: rework mem_cgroup_iter to use cgroup iterators Michal Hocko
2013-01-03 17:54 ` [PATCH v3 4/7] memcg: remove memcg from the reclaim iterators Michal Hocko
2013-01-07 6:18 ` Kamezawa Hiroyuki
2013-02-08 19:33 ` Johannes Weiner
2013-02-11 15:16 ` Michal Hocko
2013-02-11 17:56 ` Johannes Weiner
2013-02-11 19:29 ` Michal Hocko
2013-02-11 19:58 ` Johannes Weiner
2013-02-11 21:27 ` Michal Hocko
2013-02-11 22:07 ` Michal Hocko
2013-02-11 22:39 ` Johannes Weiner
2013-02-12 9:54 ` Michal Hocko
2013-02-12 15:10 ` Johannes Weiner
2013-02-12 15:43 ` Michal Hocko
2013-02-12 16:10 ` Paul E. McKenney
2013-02-12 17:25 ` Johannes Weiner
2013-02-12 18:31 ` Paul E. McKenney
2013-02-12 19:53 ` Johannes Weiner
2013-02-13 9:51 ` Michal Hocko
2013-02-12 17:56 ` Michal Hocko
2013-02-12 16:13 ` Michal Hocko
2013-02-12 16:24 ` Michal Hocko
2013-02-12 16:37 ` Michal Hocko
2013-02-12 16:41 ` Johannes Weiner
2013-02-12 17:12 ` Michal Hocko [this message]
2013-02-12 17:37 ` Johannes Weiner
2013-02-13 8:11 ` Glauber Costa
2013-02-13 10:38 ` Michal Hocko
2013-02-13 10:34 ` Michal Hocko
2013-02-13 12:56 ` Michal Hocko
2013-02-12 16:33 ` Johannes Weiner
2013-01-03 17:54 ` [PATCH v3 5/7] memcg: simplify mem_cgroup_iter Michal Hocko
2013-01-03 17:54 ` [PATCH v3 6/7] memcg: further " Michal Hocko
2013-01-03 17:54 ` [PATCH v3 7/7] cgroup: remove css_get_next Michal Hocko
2013-01-04 3:42 ` Li Zefan
2013-01-23 12:52 ` [PATCH v3 0/7] rework mem_cgroup iterator Michal Hocko
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=20130212171216.GA17663@dhcp22.suse.cz \
--to=mhocko@suse.cz \
--cc=glommer@parallels.com \
--cc=hannes@cmpxchg.org \
--cc=htejun@gmail.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizefan@huawei.com \
--cc=yinghan@google.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