From: linuxtestproject.agent@gmail.com
To: Yeswanth Krishna Tellakula <yeswanth@linux.ibm.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] cgroup/cgroup_core03: convert to new LTP API with parameterised subtests
Date: Sat, 1 Aug 2026 07:30:11 +0000 [thread overview]
Message-ID: <20260801073011.8913-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260731044216.33618-1-yeswanth@linux.ibm.com>
Hi Yeswanth,
On Fri, 31 Jul 2026, Yeswanth Krishna Tellakula wrote:
> cgroup/cgroup_core03: convert to new LTP API with parameterised subtests
> static void run(unsigned int n)
> {
> int i;
>
> /* Fork wave: only needed before the first subtest. */
> if (n == 0) {
> *data_ptr = 0;
> num_pids = PID_NUM;
>
> for (i = 0; i < num_pids; i++)
> pids[i] = cg_run_nowait(cg_child);
>
> TST_CHECKPOINT_WAIT(0);
> }
>
> switch (n) {
> case 0:
> test_cg_kill_procs_count();
> break;
> case 1:
> test_cg_kill_trigger();
Critical: Could these dependent stages remain in one .test_all callback?
After run(0) returns, run_tests() unconditionally calls
tst_reap_children(). That blocks in wait() because every child is paused,
while cgroup.kill is not written until run(1). Consequently run(1) is never
reached and the test times out.
> /*\
> * [Description]
Minor: Could the deprecated [Description] header be removed? Introductory
prose is already treated as the description, and this header is forbidden in
new C test documentation.
> .needs_root = 1,
Minor: Could the high-level description explain why root is required? The
new root-only requirement is not documented as required by the root-usage
rule.
> No functional behaviour change.
Minor: Could this claim be removed? The patch adds root-only gating and
kernel-taint failure checking, changes the timeout, and changes result
reporting, so it changes observable behavior even apart from the hang above.
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
next prev parent reply other threads:[~2026-08-01 7:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 4:42 [LTP] [PATCH] cgroup/cgroup_core03: convert to new LTP API with parameterised subtests Yeswanth Krishna Tellakula
2026-08-01 7:30 ` linuxtestproject.agent [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-31 4:19 Yeswanth Krishna Tellakula
2026-08-01 7:30 ` [LTP] " linuxtestproject.agent
2026-07-30 20:39 [LTP] [PATCH] " Yeswanth Krishna Tellakula
2026-07-31 14:28 ` [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=20260801073011.8913-1-linuxtestproject.agent@gmail.com \
--to=linuxtestproject.agent@gmail.com \
--cc=ltp@lists.linux.it \
--cc=yeswanth@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.