From: linuxtestproject.agent@gmail.com
To: yeziwen1989@yeah.net
Cc: ltp@lists.linux.it
Subject: Re: [LTP] execve05: add exit call when execve failed
Date: Fri, 5 Jun 2026 05:20:22 +0000 [thread overview]
Message-ID: <20260605052022.3971-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260605031919.5946-1-yeziwen1989@yeah.net>
Hi Yeguojin,
On Fri, 5 Jun 2026 11:19:19 +0800, Yeguojin wrote:
> execve05: add exit call when execve failed
> + exit(EXIT_FAILURE);
After tst_res(TFAIL | TTERRNO, ...) the result is already recorded by
the framework. The child's exit code is used only to detect crashes or
unexpected termination.
Once verify_execve() returns, the framework calls tst_reap_children(),
which invokes check_child_status(). That function does:
if (WEXITSTATUS(status))
tst_brk(TBROK, "Invalid child (%i) exit value %i", ...);
So exit(EXIT_FAILURE) will produce a spurious TBROK on top of the
already-reported TFAIL. The convention in LTP is to call exit(0) after
reporting a result through tst_res() in a child process.
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-05 5:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 3:19 [LTP] [PATCH] execve05: add exit call when execve failed yeziwen1989
2026-06-05 5:20 ` linuxtestproject.agent [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-05 5:44 [LTP] [PATCH] [v2] " yeziwen1989
2026-06-05 9:25 ` [LTP] " linuxtestproject.agent
2026-06-04 16:01 [LTP] [PATCH] " yeziwen1989
2026-06-04 17:55 ` [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=20260605052022.3971-1-linuxtestproject.agent@gmail.com \
--to=linuxtestproject.agent@gmail.com \
--cc=ltp@lists.linux.it \
--cc=yeziwen1989@yeah.net \
/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