All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: Richard Palethorpe <rpalethorpe@suse.com>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] controllers/cpuset: Make mount failure TCONF
Date: Fri, 27 Oct 2023 19:45:12 +0200	[thread overview]
Message-ID: <20231027174512.GA710840@pevik> (raw)
In-Reply-To: <ZTvH_DptjIrZJx-A@yuki>

> Hi!
> > > It appears that if the subsystem is available under V2 then mounting
> > > the V1 can fail. Probably when the V2 has processes assigned to a
> > > group it controls.

> > Sounds likely, but it would be good to check this in the kernel code or with
> > kernel cgroup developers.

> I'm pretty sure that controller can be used either in v1, or in v2 but
> not from both at the same time by choice. Some of the changes between v1
> and v2 are incompatible so this couldn't work either way.

> I think that once the controller name is written to
> /sys/fs/cgroup/unified/cgroup.subtree_controll mounting it to v1 should
> fail, so maybe we should just try to grep the fail instead and exit the
> test with TCONF if we found the controller bound to v2 already.

Sounds like a good idea.

Kind regards,
Petr

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

  parent reply	other threads:[~2023-10-27 17:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-27 10:49 [LTP] [PATCH] controllers/cpuset: Make mount failure TCONF Richard Palethorpe via ltp
2023-10-27 11:01 ` Petr Vorel
     [not found]   ` <ZTvH_DptjIrZJx-A@yuki>
2023-10-27 17:45     ` Petr Vorel [this message]
2023-10-30 10:39       ` Richard Palethorpe

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=20231027174512.GA710840@pevik \
    --to=pvorel@suse.cz \
    --cc=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=rpalethorpe@suse.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.