public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
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 12:25:41 +0200	[thread overview]
Message-ID: <ZEufJa+TyZdY9gsq@yuki> (raw)
In-Reply-To: <20230428084922.9834-1-liwang@redhat.com>

Hi!
> There is a tiny problem with the test logic of this tst_cgroup library,
> that it potentially mixes Cgroup V1 and V2 together to be mounted at
> the same time. The scenario happens once people just requests CTRL_BASE
> (or a V2 controller not enabled) on a only V1-mounted system.
>
> Cgroup community always objected to enabling Cgroup like that (V1&V2),
> which may bring unexpected issues along the way.
> 
> So this patch cancels LTP mount V1&V2 simultaneously even if there is
> no overlap in specific controller files.

Isn't this the point of the library, to be able to use mixed V1 and V2
setup? As far as I understand it the only limitation is that we can bind
a controllter to either V1 or V2 but not both.

Also as far as I can tell, there is pleny of distributions out there at
the moment where the default is split between V1 and V2 both mounted at
the same time.

-- 
Cyril Hrubis
chrubis@suse.cz

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2023-04-28 10:24 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 [this message]
2023-04-28 12:56   ` Li Wang
2023-04-28 13:13     ` Cyril Hrubis
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=ZEufJa+TyZdY9gsq@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