All of lore.kernel.org
 help / color / mirror / Atom feed
From: linuxtestproject.agent@gmail.com
To: Pavithra <pavrampu@linux.ibm.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] memcg/memcontrol05: add cgroup v2 task migration charge accounting test
Date: Thu, 13 Aug 2026 20:44:41 +0000	[thread overview]
Message-ID: <20260813204441.8919-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260813195418.3083880-1-pavrampu@linux.ibm.com>

Hi Pavithra,

On Fri, Aug 14, 2026, Pavithra wrote:
> memcg/memcontrol05: add cgroup v2 task migration charge accounting test

> static void cleanup(void)
> {
> 	if (group_a)
> 		group_a = tst_cg_group_rm(group_a);
> 	if (group_b)
> 		group_b = tst_cg_group_rm(group_b);
> }

Could cleanup first release and reap a worker that may still be blocked on
WORKER_RESUME or WORKER_EXIT?

Any SAFE_* failure after SAFE_FORK() enters cleanup while the worker is still
in one of these cgroups. tst_cg_group_rm() then fails to remove the populated
cgroup. After the framework kills the worker, tst_cg_cleanup() still cannot
remove the test cgroup because the child cgroup directories remain. Tracking
whether the worker was started and waking or terminating and reaping it here,
as memcontrol03/04 do, would allow the cgroups to be removed on fatal paths.

Verdict - Needs revision

---
Note:

The agent can sometimes produce false positives although often its
findings are genuine. If you find issues with the review, please
comment this email or ignore the suggestions.

Regards,
LTP AI Reviewer

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2026-08-13 20:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-13 19:54 [LTP] [PATCH v5] memcg/memcontrol05: add cgroup v2 task migration charge accounting test Pavithra
2026-08-13 20:44 ` linuxtestproject.agent [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-08-13 18:42 [LTP] [PATCH v4] " Pavithra
2026-08-13 19:06 ` [LTP] " linuxtestproject.agent
2026-08-13 16:23 [LTP] [PATCH v3] " Pavithra
2026-08-13 17:09 ` [LTP] " linuxtestproject.agent
2026-08-12 16:16 [LTP] [PATCH v2] " Pavithra
2026-08-12 17:07 ` [LTP] " linuxtestproject.agent
2026-08-04  9:59 [LTP] [PATCH] " Pavithra
2026-08-04 10:41 ` [LTP] " linuxtestproject.agent

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=20260813204441.8919-1-linuxtestproject.agent@gmail.com \
    --to=linuxtestproject.agent@gmail.com \
    --cc=ltp@lists.linux.it \
    --cc=pavrampu@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.