From: linuxtestproject.agent@gmail.com
To: Pavithra <pavrampu@linux.ibm.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] memcontrol04: Fix test failure by keeping pagecache children alive
Date: Mon, 27 Apr 2026 17:29:35 +0000 [thread overview]
Message-ID: <20260427172935.3996-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260427171734.621893-1-pavrampu@linux.ibm.com>
Hi Pavithra,
On Mon, 27 Apr 2026, Pavithra wrote:
> memcontrol04: Fix test failure by keeping pagecache children alive
> Signed-off-by: Sachin Sant <sachinp@linux.ibm.com>, Pavithra <pavrampu@linux.ibm.com>
Each contributor must have their own Signed-off-by line:
Signed-off-by: Sachin Sant <sachinp@linux.ibm.com>
Signed-off-by: Pavithra <pavrampu@linux.ibm.com>
This is a bug fix; please add a Fixes: tag pointing to the commit that
introduced the broken behaviour.
> + for (i = ARRAY_SIZE(leaf_cg); i > 0; i--) {
> + if (!leaf_cg[i - 1])
> + continue;
> +
> + TST_CHECKPOINT_WAKE2(TEST_DONE,
> + ARRAY_SIZE(leaf_cg) - 1);
> + tst_reap_children();
> + break;
> + }
ARRAY_SIZE(leaf_cg) - 1 = 3 assumes all three pagecache children were
created. If cleanup() is invoked during partial setup, TST_CHECKPOINT_WAKE2
will time out waiting for missing processes and emit a spurious TBROK.
Track the number of children actually spawned and wake only that many.
---
Note:
Our agent completed the review of the patch.
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
prev parent reply other threads:[~2026-04-27 17:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 17:17 [LTP] [PATCH] memcontrol04: Fix test failure by keeping pagecache children alive Pavithra
2026-04-27 17:29 ` linuxtestproject.agent [this message]
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=20260427172935.3996-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox