From: Michal Hocko <mhocko@kernel.org>
To: Shakeel Butt <shakeelb@google.com>
Cc: Roman Gushchin <guro@fb.com>,
linux-mm@kvack.org, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org,
Johannes Weiner <hannes@cmpxchg.org>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] mm: memcontrol: fix percpu vmstats and vmevents flush
Date: Fri, 30 Aug 2019 07:49:31 +0200 [thread overview]
Message-ID: <20190830054931.GN28313@dhcp22.suse.cz> (raw)
In-Reply-To: <20190829203110.129263-1-shakeelb@google.com>
On Thu 29-08-19 13:31:10, Shakeel Butt wrote:
> Instead of using raw_cpu_read() use per_cpu() to read the actual data of
> the corresponding cpu otherwise we will be reading the data of the
> current cpu for the number of online CPUs.
>
> Fixes: bb65f89b7d3d ("mm: memcontrol: flush percpu vmevents before releasing memcg")
> Fixes: c350a99ea2b1 ("mm: memcontrol: flush percpu vmstats before releasing memcg")
> Signed-off-by: Shakeel Butt <shakeelb@google.com>
> Cc: Roman Gushchin <guro@fb.com>
> Cc: Michal Hocko <mhocko@suse.com>
> Cc: Johannes Weiner <hannes@cmpxchg.org>
> Cc: Vladimir Davydov <vdavydov.dev@gmail.com>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: <stable@vger.kernel.org>
Ups, missed that when reviewing. Sorry about that.
Acked-by: Michal Hocko <mhocko@suse.com>
> ---
>
> Note: The buggy patches were marked for stable therefore adding Cc to
> stable.
>
> mm/memcontrol.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index 26e2999af608..f4e60ee8b845 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -3271,7 +3271,7 @@ static void memcg_flush_percpu_vmstats(struct mem_cgroup *memcg)
>
> for_each_online_cpu(cpu)
> for (i = 0; i < MEMCG_NR_STAT; i++)
> - stat[i] += raw_cpu_read(memcg->vmstats_percpu->stat[i]);
> + stat[i] += per_cpu(memcg->vmstats_percpu->stat[i], cpu);
>
> for (mi = memcg; mi; mi = parent_mem_cgroup(mi))
> for (i = 0; i < MEMCG_NR_STAT; i++)
> @@ -3286,8 +3286,8 @@ static void memcg_flush_percpu_vmstats(struct mem_cgroup *memcg)
>
> for_each_online_cpu(cpu)
> for (i = 0; i < NR_VM_NODE_STAT_ITEMS; i++)
> - stat[i] += raw_cpu_read(
> - pn->lruvec_stat_cpu->count[i]);
> + stat[i] += per_cpu(
> + pn->lruvec_stat_cpu->count[i], cpu);
>
> for (pi = pn; pi; pi = parent_nodeinfo(pi, node))
> for (i = 0; i < NR_VM_NODE_STAT_ITEMS; i++)
> @@ -3306,8 +3306,8 @@ static void memcg_flush_percpu_vmevents(struct mem_cgroup *memcg)
>
> for_each_online_cpu(cpu)
> for (i = 0; i < NR_VM_EVENT_ITEMS; i++)
> - events[i] += raw_cpu_read(
> - memcg->vmstats_percpu->events[i]);
> + events[i] += per_cpu(memcg->vmstats_percpu->events[i],
> + cpu);
>
> for (mi = memcg; mi; mi = parent_mem_cgroup(mi))
> for (i = 0; i < NR_VM_EVENT_ITEMS; i++)
> --
> 2.23.0.187.g17f5b7556c-goog
>
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2019-08-30 5:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 20:31 Shakeel Butt
2019-08-29 20:40 ` Roman Gushchin
2019-08-30 5:49 ` Michal Hocko [this message]
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=20190830054931.GN28313@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shakeelb@google.com \
--cc=stable@vger.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