All of lore.kernel.org
 help / color / mirror / Atom feed
From: linuxtestproject.agent@gmail.com
To: Pavithra <pavrampu@linux.ibm.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] Migrating the libhugetlbfs/testcases/quota.c - v2
Date: Thu,  2 Jul 2026 12:44:50 +0000	[thread overview]
Message-ID: <20260702124450.4541-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260404121120.1611032-1-pavrampu@linux.ibm.com>

Hi Pavithra,

On Sat Apr  4 17:41:20 2026 +0530, Pavithra wrote:
> Migrating the libhugetlbfs/testcases/quota.c - v2

> Migrating the libhugetlbfs/testcases/quota.c - v2

The "- v2" suffix is a patch-revision marker that must be stripped from
the final commit subject before merging.

The subject should also follow the LTP convention of naming the
subsystem and what is being added, for example:

  hugetlb/hugemmap: add hugemmap33 to test hugetlbfs quota accounting

> +/*\
> + * Test hugetlbfs quota accounting with filesystem size limits.
> + *
> + * The number of global huge pages available to a mounted hugetlbfs
> + * filesystem can be limited using a quota mechanism by setting the
> + * size attribute at mount time. Older kernels did not properly handle
> + * quota accounting in a number of cases (e.g., for MAP_PRIVATE pages,
> + * and with MAP_SHARED reservation).
> + *
> + * This test replays some scenarios on a privately mounted filesystem
> + * with quota to check for regressions in hugetlbfs quota accounting.
> + */

Ground Rule 4 requires that when a test sets .needs_root = 1, the
reason must be stated in the doc comment.  The test mounts a second
hugetlbfs instance with a quota limit in setup(), which requires
CAP_SYS_ADMIN, but the description block is silent on this.

A sentence like the following should be added:

  Root is required to mount the quota-limited hugetlbfs instance.

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

  reply	other threads:[~2026-07-02 12:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-04 12:11 [LTP] [PATCH] Migrating the libhugetlbfs/testcases/quota.c - v2 Pavithra
2026-07-02 12:44 ` linuxtestproject.agent [this message]
2026-07-02 12:50 ` Andrea Cervesato via ltp

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=20260702124450.4541-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.