diff options
author | 2014-01-21 15:49:41 -0800 | |
---|---|---|
committer | 2014-01-21 16:19:45 -0800 | |
commit | 1c98dd905ddb7552f13a3f06aa0bd9ef6affeeb7 (patch) | |
tree | 6c977f0566e6ef99ac45547a3c81017a575cd73c /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | x86, numa, acpi, memory-hotplug: make movable_node have higher priority (diff) | |
download | linux-dev-1c98dd905ddb7552f13a3f06aa0bd9ef6affeeb7.tar.xz linux-dev-1c98dd905ddb7552f13a3f06aa0bd9ef6affeeb7.zip |
memcg: fix kmem_account_flags check in memcg_can_account_kmem()
We should start kmem accounting for a memory cgroup only after both its
kmem limit is set (KMEM_ACCOUNTED_ACTIVE) and related call sites are
patched (KMEM_ACCOUNTED_ACTIVATED). Currently memcg_can_account_kmem()
allows kmem accounting even if only one of the conditions is true. Fix
it.
This means that a page might get charged by memcg_kmem_newpage_charge
which would see its static key patched already but
memcg_kmem_commit_charge would still see it unpatched and so the charge
won't be committed. The result would be charge inconsistency
(page_cgroup not marked as PageCgroupUsed) and the charge would leak
because __memcg_kmem_uncharge_pages would ignore it.
[mhocko@suse.cz: augment changelog]
Signed-off-by: Vladimir Davydov <vdavydov@parallels.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>
Acked-by: Michal Hocko <mhocko@suse.cz>
Cc: Balbir Singh <bsingharora@gmail.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Glauber Costa <glommer@parallels.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions