From: Sean Christopherson <sean.j.christopherson@intel.com>
To: mhocko@kernel.org
Cc: hannes@cmpxchg.org, vdavydov.dev@gmail.com,
cgroups@vger.kernel.org, linux-mm@kvack.org,
sean.j.christopherson@intel.com
Subject: [PATCH 2/2] mm/memcontrol: inc reclaim gen if restarting walk in mem_cgroup_iter()
Date: Fri, 28 Apr 2017 14:55:47 -0700 [thread overview]
Message-ID: <1493416547-19212-3-git-send-email-sean.j.christopherson@intel.com> (raw)
In-Reply-To: <1493416547-19212-1-git-send-email-sean.j.christopherson@intel.com>
Increment iter->generation if a reclaimer reaches the end of the tree,
even if it restarts the hierarchy walk instead of returning NULL, i.e.
this is the reclaimer's initial call to mem_cgroup_iter(). If we don't
increment the generation, other threads that are part of the current
reclaim generation will incorrectly continue to walk the tree since
iter->generation won't be updated until one of the reclaimers reaches
the end of the hierarchy a second time.
Move the put_css(&pos->css) call below the iter->generation update
to minimize the window where a thread can see a stale generation but
consume an updated position, as iter->generation and iter->position
are not updated atomically.
Signed-off-by: Sean Christopherson <sean.j.christopherson@intel.com>
---
mm/memcontrol.c | 31 ++++++++++++++++++++++++++-----
1 file changed, 26 insertions(+), 5 deletions(-)
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index 6a7ca3c..b858245 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -740,6 +740,7 @@ struct mem_cgroup *mem_cgroup_iter(struct mem_cgroup *root,
struct cgroup_subsys_state *css = NULL;
struct mem_cgroup *memcg = NULL;
struct mem_cgroup *pos = NULL;
+ bool inc_gen = false;
if (mem_cgroup_disabled())
return NULL;
@@ -791,6 +792,14 @@ struct mem_cgroup *mem_cgroup_iter(struct mem_cgroup *root,
css = css_next_descendant_pre(css, &root->css);
if (!css) {
/*
+ * Increment the generation as the next call to
+ * css_next_descendant_pre will restart at root.
+ * Do not update iter->generation directly as we
+ * should only do so if we update iter->position.
+ */
+ inc_gen = true;
+
+ /*
* Reclaimers share the hierarchy walk, and a
* new one might jump in right at the end of
* the hierarchy - make sure they see at least
@@ -838,16 +847,28 @@ struct mem_cgroup *mem_cgroup_iter(struct mem_cgroup *root,
css_put(&pos->css);
css = NULL;
memcg = NULL;
+ inc_gen = false;
goto start;
}
- if (pos)
- css_put(&pos->css);
-
- if (!memcg)
+ /*
+ * Update iter->generation asap to minimize the window where
+ * a different thread compares against a stale generation but
+ * consumes an updated position.
+ */
+ if (inc_gen)
iter->generation++;
- else if (!prev)
+
+ /*
+ * Initialize the reclaimer's generation after the potential
+ * update to iter->generation; if we restarted the hierarchy
+ * walk then we are part of the new generation.
+ */
+ if (!prev)
reclaim->generation = iter->generation;
+
+ if (pos)
+ css_put(&pos->css);
}
out_unlock:
--
2.7.4
--
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>
next prev parent reply other threads:[~2017-04-28 21:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 21:55 [PATCH 0/2] mm/memcontrol: fix reclaim bugs in mem_cgroup_iter Sean Christopherson
2017-04-28 21:55 ` [PATCH 1/2] mm/memcontrol: check cmpxchg(iter->pos...) result in mem_cgroup_iter() Sean Christopherson
2017-04-28 21:55 ` Sean Christopherson [this message]
2017-05-02 14:03 ` [PATCH 0/2] mm/memcontrol: fix reclaim bugs in mem_cgroup_iter Michal Hocko
2017-05-02 14:20 ` Christopherson, Sean J
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=1493416547-19212-3-git-send-email-sean.j.christopherson@intel.com \
--to=sean.j.christopherson@intel.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=vdavydov.dev@gmail.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;
as well as URLs for NNTP newsgroup(s).