From: linuxtestproject.agent@gmail.com
To: Pavithra <pavrampu@linux.ibm.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] hugemmap/hugemmap38: migrate libhugetlbfs test truncate_reserve_wraparound.c
Date: Fri, 17 Jul 2026 19:12:33 +0000 [thread overview]
Message-ID: <20260717191233.4148-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260717180638.1203715-1-pavrampu@linux.ibm.com>
Hi Pavithra,
On Fri, 17 Jul 2026 19:06:43 +0000, Pavithra wrote:
> hugemmap/hugemmap38: migrate libhugetlbfs test truncate_reserve_wraparound.c
> + .hugepages = {4, TST_NEEDS},
The test calls SAFE_MMAP once for hpage_size (one hugepage) and has no
other mappings. With TST_NEEDS the framework will skip the test unless
at least four hugepages are available, which is unnecessarily
restrictive.
Should this be {1, TST_NEEDS}?
> +static void setup(void)
> +{
> +
> + hpage_size = tst_get_hugepage_size();
There is an extra blank line between the opening brace and the first
statement. Linux kernel coding style does not allow blank lines at the
start of a function body.
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-17 19:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 18:06 [LTP] [PATCH] hugemmap/hugemmap38: migrate libhugetlbfs test truncate_reserve_wraparound.c Pavithra
2026-07-17 19:12 ` 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=20260717191233.4148-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.