From: Waiman Long <longman@redhat.com>
To: Tejun Heo <tj@kernel.org>
Cc: "Michal Koutný" <mkoutny@suse.com>,
"Chen Ridong" <chenridong@huawei.com>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Shuah Khan" <skhan@linuxfoundation.org>,
cgroups@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
"Xie Maoyi" <maoyi.xie@ntu.edu.sg>
Subject: Re: [PATCH] cgroup/cpuset: Creating or adding CPUs to partition not allowed without privilege
Date: Tue, 28 Apr 2026 14:02:10 -0400 [thread overview]
Message-ID: <973442ef-ad08-4503-8afc-c97d07298c61@redhat.com> (raw)
In-Reply-To: <afDVwO-j2UOdSpQj@slm.duckdns.org>
On 4/28/26 11:44 AM, Tejun Heo wrote:
> Hello,
>
> On Tue, Apr 28, 2026 at 11:19:16AM -0400, Waiman Long wrote:
> ...
>> Thank for the comment. Yes, that can be a valid configuration.
>>
>> One possible workaround may be to see if the current user has write access
>> to its parent partition root. If so, we can allow it to create a
>> sub-partition, if not, we will forbid it.
> I think this whole thing is a confusion. First of all, resource knobs in any
> given cgroup is owned by the parent. Delegations where the perm to a
> resource knob is given to delegatee is not supported and expected to affect
> resource distribution w.r.t. its siblings. Partition isn't special in this
> regard. memory.low or min can create similar effects. Maybe I'm missing
> something but I don't see anything happening that's not supposed to happen.
You are right. I am a bit confused about the exact delegation rules.
After reading the delegation section of the cgroup-v2.rst file, I
realize that the current behavior should be OK. For clarity, I am
planning to send a documentation patch to clarify the current partition
delegation behavior.
Thanks,
Longman
next prev parent reply other threads:[~2026-04-28 18:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 3:34 [PATCH] cgroup/cpuset: Creating or adding CPUs to partition not allowed without privilege Waiman Long
2026-04-28 7:58 ` Michal Koutný
2026-04-28 15:19 ` Waiman Long
2026-04-28 15:44 ` Tejun Heo
2026-04-28 18:02 ` Waiman Long [this message]
2026-04-28 15:49 ` Waiman Long
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=973442ef-ad08-4503-8afc-c97d07298c61@redhat.com \
--to=longman@redhat.com \
--cc=cgroups@vger.kernel.org \
--cc=chenridong@huawei.com \
--cc=corbet@lwn.net \
--cc=hannes@cmpxchg.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maoyi.xie@ntu.edu.sg \
--cc=mkoutny@suse.com \
--cc=skhan@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=tj@kernel.org \
/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