From: linuxtestproject.agent@gmail.com
To: Pavithra <pavrampu@linux.ibm.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] hugemmap35: Migrating libhugetlbfs test v6 truncate_reserve_wraparound.c
Date: Thu, 2 Jul 2026 12:42:01 +0000 [thread overview]
Message-ID: <20260702124201.4073-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260404171614.1695371-1-pavrampu@linux.ibm.com>
Hi Pavithra,
On Sat Apr 4 22:46:14 2026 +0530, Pavithra wrote:
> hugemmap35: Migrating libhugetlbfs test v6 truncate_reserve_wraparound.c
The "v6" in the subject looks like a series revision tag left over from
git-send-email. The libhugetlbfs source file has no "v6" in its name
(the Origin URL confirms this). Please strip it before resubmitting.
Suggested subject:
"hugemmap35: migrate libhugetlbfs test truncate_reserve_wraparound.c"
> +/*
> + * Origin: https://github.com/libhugetlbfs/libhugetlbfs/blob/master/tests/truncate_reserve_wraparound.c
> + *
> + * Test that hugepage reservation accounting is correctly maintained when
> + * truncating a hugetlbfs file. This verifies that reserved hugepages are
> + * properly tracked through the complete lifecycle
> + */
The description block must open with `/*\` (backslash after the opening
`/*`) to be recognised as RST content and exported to the test catalog.
A plain `/* */` comment is not rendered there.
The `Origin:` URL is also inside what should be the RST doc block. It
belongs in a separate plain `/* */` comment before the `/*\ ... */`
block, or can simply be omitted (the commit message and .tags already
record the provenance).
Rule 4 also requires documenting why root is needed. Hugetlbfs has to
be mounted by root, so a sentence to that effect belongs in the block.
Suggested restructure:
/*
* Origin: https://github.com/libhugetlbfs/libhugetlbfs/blob/...
*/
/*\
* Test that hugepage reservation accounting is correctly maintained
* when truncating a hugetlbfs file. This verifies that reserved
* hugepages are properly tracked through the sequence of: mmap
* (reserves page), touch (instantiates page), truncate (releases
* page), and attempted access (triggers SIGBUS). A bug in i_size
* handling could cause the reservation count to become incorrect,
* leading to resource leaks or allocation failures.
*
* Requires root to mount hugetlbfs.
*/
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:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-04 17:16 [LTP] [PATCH] hugemmap35: Migrating libhugetlbfs test v6 truncate_reserve_wraparound.c Pavithra
2026-07-02 12:42 ` 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=20260702124201.4073-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