From: Maarten Lankhorst <dev@lankhorst.se>
To: "Friedrich Vock" <friedrich.vock@gmx.de>,
"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: Maxime Ripard <mripard@kernel.org>,
dri-devel@lists.freedesktop.org, cgroups@vger.kernel.org
Subject: Re: [PATCH v2] cgroup/dmem: Don't open-code css_for_each_descendant_pre
Date: Tue, 18 Feb 2025 15:55:43 +0100 [thread overview]
Message-ID: <7f799ba1-3776-49bd-8a53-dc409ef2afe3@lankhorst.se> (raw)
In-Reply-To: <20250127152754.21325-1-friedrich.vock@gmx.de>
Hey,
Should this fix go through the cgroup tree?
Cheers,
~Maarten
On 2025-01-27 16:27, Friedrich Vock wrote:
> The current implementation has a bug: 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.
>
> Since we can just check whether a pool refers to the same region to
> determine whether or not it's related, all the additional pool tracking
> is unnecessary, so just switch to using css_for_each_descendant_pre for
> traversal.
>
> Fixes: b168ed458 ("kernel/cgroup: Add "dmem" memory accounting cgroup")
> Signed-off-by: Friedrich Vock <friedrich.vock@gmx.de>
> ---
>
> v2 (Michal): Switch to the more idiomatic css_for_each_descendant_pre
> instead of fixing the open-coded version
>
> ---
> kernel/cgroup/dmem.c | 50 ++++++++++----------------------------------
> 1 file changed, 11 insertions(+), 39 deletions(-)
>
> diff --git a/kernel/cgroup/dmem.c b/kernel/cgroup/dmem.c
> index 52736ef0ccf2..77d9bb1c147f 100644
> --- a/kernel/cgroup/dmem.c
> +++ b/kernel/cgroup/dmem.c
> @@ -220,60 +220,32 @@ dmem_cgroup_calculate_protection(struct dmem_cgroup_pool_state *limit_pool,
> struct dmem_cgroup_pool_state *test_pool)
> {
> struct page_counter *climit;
> - struct cgroup_subsys_state *css, *next_css;
> + struct cgroup_subsys_state *css;
> struct dmemcg_state *dmemcg_iter;
> - struct dmem_cgroup_pool_state *pool, *parent_pool;
> - bool found_descendant;
> + struct dmem_cgroup_pool_state *pool, *found_pool;
>
> climit = &limit_pool->cnt;
>
> rcu_read_lock();
> - parent_pool = pool = limit_pool;
> - css = &limit_pool->cs->css;
>
> - /*
> - * This logic is roughly equivalent to css_foreach_descendant_pre,
> - * except we also track the parent pool to find out which pool we need
> - * to calculate protection values for.
> - *
> - * We can stop the traversal once we find test_pool among the
> - * descendants since we don't really care about any others.
> - */
> - while (pool != test_pool) {
> - next_css = css_next_child(NULL, css);
> - if (next_css) {
> - parent_pool = pool;
> - } else {
> - while (css != &limit_pool->cs->css) {
> - next_css = css_next_child(css, css->parent);
> - if (next_css)
> - break;
> - css = css->parent;
> - parent_pool = pool_parent(parent_pool);
> - }
> - /*
> - * We can only hit this when test_pool is not a
> - * descendant of limit_pool.
> - */
> - if (WARN_ON_ONCE(css == &limit_pool->cs->css))
> - break;
> - }
> - css = next_css;
> -
> - found_descendant = false;
> + css_for_each_descendant_pre(css, &limit_pool->cs->css) {
> dmemcg_iter = container_of(css, struct dmemcg_state, css);
> + found_pool = NULL;
>
> list_for_each_entry_rcu(pool, &dmemcg_iter->pools, css_node) {
> - if (pool_parent(pool) == parent_pool) {
> - found_descendant = true;
> + if (pool->region == limit_pool->region) {
> + found_pool = pool;
> break;
> }
> }
> - if (!found_descendant)
> + if (!found_pool)
> continue;
>
> page_counter_calculate_protection(
> - climit, &pool->cnt, true);
> + climit, &found_pool->cnt, true);
> +
> + if (found_pool == test_pool)
> + break;
> }
> rcu_read_unlock();
> }
> --
> 2.48.0
>
next prev parent reply other threads:[~2025-02-18 14:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 15:39 [PATCH] cgroup/dmem: Don't clobber pool in dmem_cgroup_calculate_protection Friedrich Vock
2025-01-14 15:58 ` 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 [this message]
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=7f799ba1-3776-49bd-8a53-dc409ef2afe3@lankhorst.se \
--to=dev@lankhorst.se \
--cc=airlied@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=friedrich.vock@gmx.de \
--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