From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: priyama2 <priyama2@linux.ibm.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] RFC: Proposed cgroup v2 and openat2 test case contributions for LTP
Date: Thu, 18 Jun 2026 11:35:38 +0000 [thread overview]
Message-ID: <6a33d80b.cf2df9a4.12392.26f4@mx.google.com> (raw)
In-Reply-To: <f3181c24-f3b8-4083-ac42-fb2da6cfa8a1@linux.ibm.com>
Hi Priyama,
the cgroup testing suite in LTP can be a bit unstable due to the nature
of cgroup v1 -> v2 migration. The V2 seems stable, but sometimes tests
might produce false positives, mostly related to system configurations
or system overload. We digged quite a lot into it in the past years and
we ended up with a solution which "good enough" for regression testing,
supporting both v1 and v2.
Also, kselftests already cover many cgroup testing scenarios and we are
not actively investing time on it. But you and others are welcome to try
implementing something, if you think this can be helpful.
My biggest concern is the code quality. cgroups can be a complex beast
to handle with LTP API, which are made supporting v1 and v2.
If you are willing to implement new tests, please consider test cases
scenarios that are not implemented in LTP and kselftests. Those are the
most valuable at the moment.
Regards,
--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-06-18 11:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 3:26 [LTP] RFC: Proposed cgroup v2 and openat2 test case contributions for LTP priyama2
2026-06-18 11:35 ` Andrea Cervesato via ltp [this message]
2026-06-18 14:14 ` Sebastian Chlad
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=6a33d80b.cf2df9a4.12392.26f4@mx.google.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=priyama2@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