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] memcg/memcontrol05: add cgroup v2 task migration charge accounting test
Date: Wed, 12 Aug 2026 17:07:40 +0000	[thread overview]
Message-ID: <20260812170740.9021-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260812161613.2715489-1-pavrampu@linux.ibm.com>

Hi Pavithra,

On Aug 12, 2026, Pavithra wrote:
> memcg/memcontrol05: add cgroup v2 task migration charge accounting test

> +#define ALLOC_SIZE	MB(60)
> +#define ALLOC_SIZE2	MB(20)
> +#define MIN_MEM_AVAIL	80

[Medium] Could MIN_MEM_AVAIL include headroom above the two mappings? The
worker keeps both mappings resident simultaneously, so a host with exactly
80 MiB available passes the framework check but still needs memory for page
tables and other process and kernel allocations. The worker can be OOM-killed
while touching the mappings, producing a timeout or TBROK instead of testing
charge accounting.

> +	SAFE_CG_SCANF(group_b, "memory.current", "%ld", &after_migrate);
> +	TST_EXP_EXPR(after_migrate <= baseline_b + (long)MB(4),
> +		     "group_b memory.current (%ld) not increased after migration (baseline=%ld)",
> +		     after_migrate, baseline_b);

[Medium] Could this also read and verify group_a/memory.current after the
migration? The stated invariant is that existing charges remain pinned to
group_a, but this checks only that group_b did not gain them. A regression
that drops those charges during migration leaves group_b within the allowed
range and reports TPASS despite violating the invariant.

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-08-12 17:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-12 16:16 [LTP] [PATCH v2] memcg/memcontrol05: add cgroup v2 task migration charge accounting test Pavithra
2026-08-12 17:07 ` linuxtestproject.agent [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-08-04  9:59 [LTP] [PATCH] " Pavithra
2026-08-04 10:41 ` [LTP] " linuxtestproject.agent

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