From: linuxtestproject.agent@gmail.com
To: Jinseok Kim <always.starving0@gmail.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] syscalls: Replace getppid02 with getpid02 implementation
Date: Tue, 7 Jul 2026 16:34:11 +0000 [thread overview]
Message-ID: <20260707163411.4006-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260707153502.15421-1-always.starving0@gmail.com>
Hi Jinseok,
On Tue, 07 Jul 2026 16:31:02 +0000, Jinseok Kim wrote:
> syscalls: Replace getppid02 with getpid02 implementation
> Remove the existing getppid02.c as its coverage is overlapped by
> getpid02.c. Then, replace it by renaming and adapting the broader checks
> from getpid02.c to serve as the new getppid02.c.
The commit message says "Remove the existing getppid02.c" but the file
that is actually deleted is getpid02.c. getppid02.c is replaced, not
removed. The sentence reads as if getppid02.c disappears, which is the
opposite of what happens.
> +static void verify_getpid(void)
This function is in getppid02.c but the name still says `verify_getpid`.
The function tests both fork/getpid consistency and getppid correctness,
but it was copied from getpid02.c without renaming. Could it be renamed
to `verify_getppid` to match the file it now lives in?
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
prev parent reply other threads:[~2026-07-07 16:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 15:35 [LTP] [PATCH] syscalls: Replace getppid02 with getpid02 implementation Jinseok Kim
2026-07-07 16:34 ` 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=20260707163411.4006-1-linuxtestproject.agent@gmail.com \
--to=linuxtestproject.agent@gmail.com \
--cc=always.starving0@gmail.com \
--cc=ltp@lists.linux.it \
/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