From: Michal Hocko <mhocko@suse.com>
To: Muchun Song <songmuchun@bytedance.com>
Cc: hannes@cmpxchg.org, vdavydov.dev@gmail.com,
akpm@linux-foundation.org, cgroups@vger.kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] mm: memcontrol: bail out early when id is zero
Date: Mon, 15 Feb 2021 10:39:30 +0100 [thread overview]
Message-ID: <YCpBUm2N4Bqm5PM5@dhcp22.suse.cz> (raw)
In-Reply-To: <20210212170159.32153-3-songmuchun@bytedance.com>
On Sat 13-02-21 01:01:58, Muchun Song wrote:
> The memcg ID cannot be zero, but we can pass zero to mem_cgroup_from_id,
> so idr_find() is pointless and wastes CPU cycles.
Is this possible at all to happen? If not why should we add a test for
_all_ invocations?
>
> Signed-off-by: Muchun Song <songmuchun@bytedance.com>
> ---
> mm/memcontrol.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index a3f26522765a..68ed4b297c13 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -5173,6 +5173,9 @@ static inline void mem_cgroup_id_put(struct mem_cgroup *memcg)
> struct mem_cgroup *mem_cgroup_from_id(unsigned short id)
> {
> WARN_ON_ONCE(!rcu_read_lock_held());
> + /* The memcg ID cannot be zero. */
> + if (id == 0)
> + return NULL;
> return idr_find(&mem_cgroup_idr, id);
> }
>
> --
> 2.11.0
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2021-02-15 9:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 17:01 [PATCH 1/4] mm: memcontrol: remove memcg check from memcg_oom_recover Muchun Song
2021-02-12 17:01 ` [PATCH 2/4] mm: memcontrol: add missing memcg_oom_recover() when uncharge slab page Muchun Song
2021-02-15 9:37 ` Michal Hocko
2021-02-12 17:01 ` [PATCH 3/4] mm: memcontrol: bail out early when id is zero Muchun Song
2021-02-15 9:39 ` Michal Hocko [this message]
2021-02-15 10:09 ` [External] " Muchun Song
2021-02-15 10:27 ` Michal Hocko
2021-02-15 11:34 ` Muchun Song
2021-02-12 17:01 ` [PATCH 4/4] mm: memcontrol: fix swap uncharge on cgroup v2 Muchun Song
2021-02-12 18:56 ` Shakeel Butt
2021-02-13 6:48 ` [External] " Muchun Song
2021-02-16 17:16 ` Shakeel Butt
2021-02-15 9:47 ` Michal Hocko
2021-02-15 10:15 ` [External] " Muchun Song
2021-02-15 10:24 ` Michal Hocko
2021-02-16 16:59 ` Johannes Weiner
2021-02-16 17:17 ` Shakeel Butt
2021-02-16 17:19 ` Michal Hocko
2021-02-16 17:28 ` Johannes Weiner
2021-02-17 5:15 ` [External] " Muchun Song
2021-02-17 5:11 ` Muchun Song
2021-02-15 9:24 ` [PATCH 1/4] mm: memcontrol: remove memcg check from memcg_oom_recover 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=YCpBUm2N4Bqm5PM5@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=songmuchun@bytedance.com \
--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