From: Friedrich Vock <friedrich.vock@gmx.de>
To: "Tejun Heo" <tj@kernel.org>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Michal Koutný" <mkoutny@suse.com>,
"Simona Vetter" <simona.vetter@ffwll.ch>,
"David Airlie" <airlied@gmail.com>
Cc: Maarten Lankhorst <dev@lankhorst.se>,
Maxime Ripard <mripard@kernel.org>,
dri-devel@lists.freedesktop.org, cgroups@vger.kernel.org
Subject: [PATCH] cgroup/dmem: Don't clobber pool in dmem_cgroup_calculate_protection
Date: Tue, 14 Jan 2025 16:39:12 +0100 [thread overview]
Message-ID: <20250114153912.278909-1-friedrich.vock@gmx.de> (raw)
If the current css doesn't contain any pool that is a descendant of
the "pool" (i.e. when found_descendant == false), then "pool" will
point to some unrelated pool. If the current css has a child, we'll
overwrite parent_pool with this unrelated pool on the next iteration.
Fix this by overwriting "pool" only if it actually is a descendant of
parent_pool, and setting it to NULL otherwise. Also, skip traversing
subtrees if pool == NULL to avoid overwriting parent_pool (and because
it's pointless).
Fixes: b168ed458 ("kernel/cgroup: Add "dmem" memory accounting cgroup")
Signed-off-by: Friedrich Vock <friedrich.vock@gmx.de>
---
kernel/cgroup/dmem.c | 21 +++++++++++++--------
1 file changed, 13 insertions(+), 8 deletions(-)
diff --git a/kernel/cgroup/dmem.c b/kernel/cgroup/dmem.c
index 52736ef0ccf25..10d37df5d50f6 100644
--- a/kernel/cgroup/dmem.c
+++ b/kernel/cgroup/dmem.c
@@ -222,8 +222,7 @@ dmem_cgroup_calculate_protection(struct dmem_cgroup_pool_state *limit_pool,
struct page_counter *climit;
struct cgroup_subsys_state *css, *next_css;
struct dmemcg_state *dmemcg_iter;
- struct dmem_cgroup_pool_state *pool, *parent_pool;
- bool found_descendant;
+ struct dmem_cgroup_pool_state *pool, *candidate_pool, *parent_pool;
climit = &limit_pool->cnt;
@@ -241,7 +240,13 @@ dmem_cgroup_calculate_protection(struct dmem_cgroup_pool_state *limit_pool,
*/
while (pool != test_pool) {
next_css = css_next_child(NULL, css);
- if (next_css) {
+ /*
+ * pool is NULL when the current css does not contain a
+ * pool of the type we're interested in. In that case, it's
+ * impossible that any child css contains a relevant pool, so
+ * skip the subtree entirely and move on to the next sibling.
+ */
+ if (next_css && pool) {
parent_pool = pool;
} else {
while (css != &limit_pool->cs->css) {
@@ -260,16 +265,16 @@ dmem_cgroup_calculate_protection(struct dmem_cgroup_pool_state *limit_pool,
}
css = next_css;
- found_descendant = false;
dmemcg_iter = container_of(css, struct dmemcg_state, css);
- list_for_each_entry_rcu(pool, &dmemcg_iter->pools, css_node) {
- if (pool_parent(pool) == parent_pool) {
- found_descendant = true;
+ pool = NULL;
+ list_for_each_entry_rcu(candidate_pool, &dmemcg_iter->pools, css_node) {
+ if (pool_parent(candidate_pool) == parent_pool) {
+ pool = candidate_pool;
break;
}
}
- if (!found_descendant)
+ if (!pool)
continue;
page_counter_calculate_protection(
--
2.48.0
next reply other threads:[~2025-01-14 15:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 15:39 Friedrich Vock [this message]
2025-01-14 15:58 ` [PATCH] cgroup/dmem: Don't clobber pool in dmem_cgroup_calculate_protection Michal Koutný
2025-01-16 8:20 ` Friedrich Vock
2025-01-17 17:29 ` Michal Koutný
2025-01-17 19:02 ` Friedrich Vock
2025-01-24 9:56 ` Michal Koutný
2025-01-26 16:38 ` Friedrich Vock
2025-01-27 15:27 ` [PATCH v2] cgroup/dmem: Don't open-code css_for_each_descendant_pre Friedrich Vock
2025-02-12 8:40 ` Maarten Lankhorst
2025-02-18 14:55 ` Maarten Lankhorst
2025-02-18 18:39 ` Tejun Heo
2025-02-19 8:53 ` Maarten Lankhorst
2025-02-19 9:08 ` Maxime Ripard
2025-02-19 13:26 ` Simona Vetter
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=20250114153912.278909-1-friedrich.vock@gmx.de \
--to=friedrich.vock@gmx.de \
--cc=airlied@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=dev@lankhorst.se \
--cc=dri-devel@lists.freedesktop.org \
--cc=hannes@cmpxchg.org \
--cc=mkoutny@suse.com \
--cc=mripard@kernel.org \
--cc=simona.vetter@ffwll.ch \
--cc=tj@kernel.org \
/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