From: linuxtestproject.agent@gmail.com
To: Shaojie Sun <sunshaojie@kylinos.cn>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] tst_cgroup: add cpu.stat and cpu.weight to cgroup file table
Date: Fri, 31 Jul 2026 06:20:21 +0000 [thread overview]
Message-ID: <20260731062021.4129-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260731031343.1298712-2-sunshaojie@kylinos.cn>
Hi Shaojie,
On 2026-07-31, Shaojie Sun wrote:
> tst_cgroup: add cpu.stat and cpu.weight to cgroup file table
--- [PATCH 2/3] ---
> +# SPDX-License-Identifier: GPL-2.0-or-later
> +
> +top_srcdir ?= ../../../..
The build system convention is an SPDX line followed by a Copyright
line; the sibling controller Makefiles (memcg, cgroup) carry one. Could
a Copyright line be added here?
> +LDLIBS += -lpthread
This flag is applied directory-wide, but cgroup_cpu01.c does not include
cgroup_cpu_common.h and uses no pthreads. Would a per-target assignment
for the tests that actually need it be cleaner?
> +static struct tst_test test = {
> + .cleanup = cleanup,
> + .test_all = test_cpucg_subtree_control,
> + .needs_cgroup_ver = TST_CG_V2,
> + .needs_cgroup_ctrls = (const char *const []){ "cpu", NULL },
> +};
cgroup_cpu02..05 set .needs_root = 1, but this test does not, even
though it creates nested cgroups and writes cgroup.subtree_control. Is
the omission intentional?
> +/*
> + * Copyright (c) 2025 Richard Palethorpe <rpalethorpe@suse.com>
> + */
The other four test files and the shared header also credit the porting
author (2026). Should cgroup_cpu01.c carry the same attribution for
consistency?
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
next prev parent reply other threads:[~2026-07-31 6:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 12:25 [LTP] [PATCH v2 0/3] Add CPU cgroup v2 tests ported from kselftest Shaojie Sun
2026-07-30 12:25 ` [LTP] [PATCH v2 1/3] tst_cgroup: add cpu.stat and cpu.weight to cgroup file table Shaojie Sun
2026-07-30 14:06 ` [LTP] " linuxtestproject.agent
2026-07-31 3:13 ` [LTP] [PATCH v3 0/3] Add CPU cgroup v2 tests ported from kselftest Shaojie Sun
2026-07-31 3:13 ` [LTP] [PATCH v3 1/3] tst_cgroup: add cpu.stat and cpu.weight to cgroup file table Shaojie Sun
2026-07-31 6:20 ` linuxtestproject.agent [this message]
2026-07-31 3:13 ` [LTP] [PATCH v3 2/3] cgroup: add CPU cgroup v2 tests ported from kselftest Shaojie Sun
2026-07-31 3:13 ` [LTP] [PATCH v3 3/3] runtest/controllers: add CPU cgroup v2 test entries Shaojie Sun
2026-07-31 8:20 ` [LTP] [PATCH v3 0/3] Add CPU cgroup v2 tests ported from kselftest Andrea Cervesato via ltp
2026-07-30 12:25 ` [LTP] [PATCH v2 2/3] cgroup: add " Shaojie Sun
2026-07-30 12:25 ` [LTP] [PATCH v2 3/3] runtest/controllers: add CPU cgroup v2 test entries Shaojie Sun
-- strict thread matches above, loose matches on Subject: below --
2026-07-30 3:28 [LTP] [PATCH 1/3] tst_cgroup: add cpu.stat and cpu.weight to cgroup file table Shaojie Sun
2026-07-30 7:04 ` [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=20260731062021.4129-1-linuxtestproject.agent@gmail.com \
--to=linuxtestproject.agent@gmail.com \
--cc=ltp@lists.linux.it \
--cc=sunshaojie@kylinos.cn \
/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.