From: Qian Cai <cai@lca.pw>
To: akpm@linux-foundation.org
Cc: miles.chen@mediatek.com, mhocko@suse.com, hannes@cmpxchg.org,
vdavydov.dev@gmail.com, cgroups@vger.kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Qian Cai <cai@lca.pw>
Subject: [PATCH -next] mm/memcg: fix a -Wparentheses compilation warning
Date: Wed, 31 Jul 2019 09:45:53 -0400 [thread overview]
Message-ID: <1564580753-17531-1-git-send-email-cai@lca.pw> (raw)
The linux-next commit ("mm/memcontrol.c: fix use after free in
mem_cgroup_iter()") [1] introduced a compilation warning,
mm/memcontrol.c:1160:17: warning: using the result of an assignment as a
condition without parentheses [-Wparentheses]
} while (memcg = parent_mem_cgroup(memcg));
~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~
mm/memcontrol.c:1160:17: note: place parentheses around the assignment
to silence this warning
} while (memcg = parent_mem_cgroup(memcg));
^
( )
mm/memcontrol.c:1160:17: note: use '==' to turn this assignment into an
equality comparison
} while (memcg = parent_mem_cgroup(memcg));
^
==
Fix it by adding a pair of parentheses.
[1] https://lore.kernel.org/linux-mm/20190730015729.4406-1-miles.chen@mediatek.com/
Signed-off-by: Qian Cai <cai@lca.pw>
---
mm/memcontrol.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index 694b6f8776dc..4f66a8305ae0 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -1157,7 +1157,7 @@ static void invalidate_reclaim_iterators(struct mem_cgroup *dead_memcg)
do {
__invalidate_reclaim_iterators(memcg, dead_memcg);
last = memcg;
- } while (memcg = parent_mem_cgroup(memcg));
+ } while ((memcg = parent_mem_cgroup(memcg)));
/*
* When cgruop1 non-hierarchy mode is used,
--
1.8.3.1
next reply other threads:[~2019-07-31 13:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 13:45 Qian Cai [this message]
2019-07-31 13:53 ` [PATCH -next] mm/memcg: fix a -Wparentheses compilation warning 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=1564580753-17531-1-git-send-email-cai@lca.pw \
--to=cai@lca.pw \
--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=mhocko@suse.com \
--cc=miles.chen@mediatek.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;
as well as URLs for NNTP newsgroup(s).