From: Cyril Hrubis <chrubis@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [RFC PATCH] tst_cgroup: Avoid mixing mounts V1 and V2 simultaneously
Date: Fri, 28 Apr 2023 15:13:22 +0200 [thread overview]
Message-ID: <ZEvGchayVsZfrAH5@yuki> (raw)
In-Reply-To: <CAEemH2fcvpRLS7-rdpiGt-fqEwXCiAb-jpRdisb33axhdP3CoA@mail.gmail.com>
Hi!
> That's the original design. We tried to keep flexible but ignored
> one exception V1 mounts all controllers and V2 only basic mount.
> (No controllers conflict in this mounting).
>
> From my observation, if a system(e.g. RHEL8) only announces
> Cgroup V1 support but does not guarantee V2 to be used.
> A test required 'CTRL_BASE' could mount V2 success but
> that V2 is only part work and test will get TBROK.
> We are unable to say this situation is a bug.
So the V2 does not actually work unless there is at least one controller
enabled? That sounds like a bug to me, my system actually uses v1
controllers and unified hierarchy at the same time. The unified
hierarchy is used to group deamon processes and kill them with the
cgropu.kill if needed.
What exactly happens on your system?
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-04-28 13:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 8:49 [LTP] [RFC PATCH] tst_cgroup: Avoid mixing mounts V1 and V2 simultaneously Li Wang
2023-04-28 10:25 ` Cyril Hrubis
2023-04-28 12:56 ` Li Wang
2023-04-28 13:13 ` Cyril Hrubis [this message]
2023-04-28 13:30 ` Li Wang
2023-04-29 6:47 ` Li Wang
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=ZEvGchayVsZfrAH5@yuki \
--to=chrubis@suse.cz \
--cc=liwang@redhat.com \
--cc=ltp@lists.linux.it \
/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