From: linuxtestproject.agent@gmail.com
To: Wei Gao <wegao@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] mmapstress06: Convert to new API
Date: Sat, 6 Jun 2026 11:32:02 +0000 [thread overview]
Message-ID: <20260606113202.4034-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260606100823.32067-1-wegao@suse.com>
Hi Wei,
On Sat, 06 Jun 2026 10:08:05 +0000, Wei Gao wrote:
> mmapstress06: Convert to new API
> + SAFE_WAITPID(child_pid, &status, 0);
> + child_pid = -1;
> +
> + if (!WIFEXITED(status) || WEXITSTATUS(status) != 0)
> + tst_res(TFAIL, "Child process failed (status: %d)", status);
The child already calls tst_res(TPASS/TFAIL, ...) directly, and
.forks_child = 1 tells the framework to propagate those results to the
parent. Checking WEXITSTATUS on top of that risks double-reporting: if a
SAFE_* macro in the child triggers tst_brk(), the framework records the
TBROK from the child and the parent then logs an additional TFAIL.
The correct pattern (per the LTP rules on child result reporting) is to
rely on tst_res() in the child and drop the exit-code check in the
parent. SAFE_WAITPID() is still needed to reap the child, but the result
is already reported:
SAFE_WAITPID(child_pid, &status, 0);
child_pid = -1;
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-06-06 11:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 11:59 [LTP] [PATCH v1] mmapstress06: TCONF on systems without swap space Wei Gao via ltp
2026-04-27 12:26 ` Li Wang
2026-04-27 13:57 ` Wei Gao via ltp
2026-04-28 1:39 ` Li Wang
2026-04-27 13:57 ` [LTP] " linuxtestproject.agent
2026-04-28 11:52 ` [LTP] [PATCH v1] " Andrea Cervesato via ltp
2026-04-28 12:58 ` Petr Vorel
2026-04-28 16:34 ` Petr Vorel
2026-04-29 2:22 ` Wei Gao via ltp
2026-04-29 6:10 ` Petr Vorel
2026-04-30 8:01 ` Li Wang
2026-06-05 4:29 ` [LTP] [PATCH v2] mmapstress06: Convert to new API Wei Gao via ltp
2026-06-05 5:28 ` [LTP] " linuxtestproject.agent
2026-06-05 7:11 ` Li Wang
2026-06-05 7:17 ` [LTP] [PATCH v2] " Andrea Cervesato via ltp
2026-06-05 9:35 ` Wei Gao via ltp
2026-06-05 9:42 ` Andrea Cervesato via ltp
2026-06-05 10:02 ` Wei Gao via ltp
2026-06-06 10:08 ` [LTP] [PATCH v3] " Wei Gao via ltp
2026-06-06 11:32 ` linuxtestproject.agent [this message]
2026-06-07 4:52 ` [LTP] [PATCH v4] " Wei Gao via ltp
2026-06-07 8:02 ` [LTP] " linuxtestproject.agent
2026-06-08 2:52 ` [LTP] [PATCH v5] " Wei Gao via ltp
2026-06-08 4:51 ` [LTP] " linuxtestproject.agent
2026-06-10 2:26 ` [LTP] [PATCH v5] " Li Wang
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=20260606113202.4034-1-linuxtestproject.agent@gmail.com \
--to=linuxtestproject.agent@gmail.com \
--cc=ltp@lists.linux.it \
--cc=wegao@suse.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