From: linuxtestproject.agent@gmail.com
To: Pavithra <pavrampu@linux.ibm.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] hugemmap41: Migrate ptrace-write-hugepage from libhugetlbfs v3
Date: Thu, 2 Jul 2026 12:31:18 +0000 [thread overview]
Message-ID: <20260702123118.3964-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260404134815.1638618-1-pavrampu@linux.ibm.com>
Hi Pavithra,
On Sat, Apr 4 2026, Pavithra wrote:
> hugemmap41: Migrate ptrace-write-hugepage from libhugetlbfs v3
The subject ends with "v3". Is that a patch revision marker that did
not get stripped before committing? If it refers to something like a
libhugetlbfs variant, please rephrase the subject to make that clear.
> +/*
> + * Test ptrace write to hugepage memory.
> + *
> + * This test verifies that ptrace POKEDATA and PEEKDATA work correctly
> + * on hugepage-backed memory regions. A child process maps a hugepage,
> + * and the parent uses ptrace to write and read data from the child's
> + * hugepage memory, ensuring that ptrace operations function properly
> + * with hugepage mappings.
> + */
The description block must open with "/*\" (backslash after the star)
so it is recognized as RST and rendered in the LTP test catalog.
Also, .needs_root = 1 is set but the block does not explain why root
is required. Ground Rule 4 requires documenting the reason here (e.g.,
ptrace(PTRACE_ATTACH) requires CAP_SYS_PTRACE when ptrace_scope > 1,
or the hugetlbfs mount operations need root).
> + SAFE_PTRACE(PTRACE_KILL, cpid, NULL, NULL);
> + SAFE_WAITPID(cpid, &status, 0);
PTRACE_KILL is deprecated. From ptrace(2): "This operation is
deprecated; do not use it!" The recommended replacement is to deliver
SIGKILL directly via kill(cpid, SIGKILL) and then wait for it.
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-02 12:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-04 13:48 [LTP] [PATCH] hugemmap41: Migrate ptrace-write-hugepage from libhugetlbfs v3 Pavithra
2026-07-02 12:31 ` 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=20260702123118.3964-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