From: Waiman Long <longman@redhat.com>
To: "Michal Koutný" <mkoutny@suse.com>
Cc: linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
linux-kselftest@vger.kernel.org,
Zefan Li <lizefan.x@bytedance.com>, Tejun Heo <tj@kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH 1/3] cpuset: Allow setscheduler regardless of manipulated task
Date: Thu, 29 Jun 2023 09:25:05 -0400 [thread overview]
Message-ID: <67d72bc7-a277-9210-6f40-d3d94f2643a0@redhat.com> (raw)
In-Reply-To: <4fowzgkh7yo5ku2fsrptyi7jzikynjtq4zpfcx7k26vk4k6zj3@ubnupp5jqgle>
On 6/29/23 08:26, Michal Koutný wrote:
> On Thu, Jun 29, 2023 at 08:11:33AM -0400, Waiman Long <longman@redhat.com> wrote:
>> So I think you should just use
>> cgroup_subsys_on_dfl(cpuset_cgrp_subsys) as the v2 check if your focus
>> is just to prevent problem when enabling cpuset controller.
> I thought the bare cgroup_subsys_on_dfl(cpuset_cgrp_subsys) is not used
> in cpuset.c but I was wrong -- yes, I'll change this.
>
>> This change will likely conflict with the latest cpuset change on tracking #
>> of dl tasks in a cpuset. You will have to, at least, move the dl task check
>> before the security_task_setscheduler() check.
>>
>> Another fact about cpuset controller enabling is that both cpus_allowed and
>> mems_allowed are empty at that point. You may also add these checks as a
>> preconditions for disabling the security_task_setscheduler check.
> Ah, I will rebase on fresh mainline (or do you mean another reference?).
Yes, those changes have just been merged into the mainline.
Cheers,
Longman
next prev parent reply other threads:[~2023-06-29 13:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 9:11 [PATCH 0/3] cpuset: Allow setscheduler regardless of manipulated task Michal Koutný
[not found] ` <20230629091146.28801-1-mkoutny-IBi9RG/b67k@public.gmane.org>
2023-06-29 9:11 ` [PATCH 1/3] " Michal Koutný
[not found] ` <20230629091146.28801-2-mkoutny-IBi9RG/b67k@public.gmane.org>
2023-06-29 12:11 ` Waiman Long
[not found] ` <15c607d9-c1fa-ca11-d675-8f2b3a6fd15b-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2023-06-29 12:26 ` Michal Koutný
2023-06-29 13:25 ` Waiman Long [this message]
2023-06-30 18:42 ` Michal Koutný
2023-06-29 9:11 ` [PATCH 2/3] selftests: cgroup: Minor code reorganizations Michal Koutný
2023-06-29 9:11 ` [PATCH 3/3] selftests: cgroup: Add cpuset migrations testcase Michal Koutný
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=67d72bc7-a277-9210-6f40-d3d94f2643a0@redhat.com \
--to=longman@redhat.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=mkoutny@suse.com \
--cc=shuah@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