mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Waiman Long <longman@redhat.com>
To: "Michal Koutný" <mkoutny@suse.com>
Cc: Tejun Heo <tj@kernel.org>, Zefan Li <lizefan.x@bytedance.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Christian Brauner <brauner@kernel.org>,
	cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
	Juri Lelli <juri.lelli@redhat.com>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	gscrivan@redhat.com
Subject: Re: [PATCH 1/3] cgroup/cpuset: Make cpuset_fork() handle CLONE_INTO_CGROUP properly
Date: Tue, 4 Apr 2023 09:52:37 -0400	[thread overview]
Message-ID: <a01585bc-03f8-e32c-ac46-99ac484a5e5d@redhat.com> (raw)
In-Reply-To: <20230404091953.tcu3zg7npstk3ztc@blackpad>


On 4/4/23 05:19, Michal Koutný wrote:
> On Mon, Apr 03, 2023 at 01:18:42PM -0400, Waiman Long <longman@redhat.com> wrote:
>> 1) PF_NO_SETAFFINITY flag - which won't be set in the case of fork() as it
>> is for kthread only.
>> 2) DL bandwidth - Juri has a cpuset outstanding to modify the way this check
>> is being done. I want to wait until it is settled before tackling this, if
>> necessary.
> BTW what about CLONE_INTO_CGROUP where the target cpuset has empty
> effective cpuset?
Good point. That will require a can_fork() method then. I will look into 
that.
>
>> 3) security_task_setscheduler() - the CLONE_INTO_CGROUP code has already
>> checked that, we don't need to duplicate the check.
> Not sure what this refers to.
It is just checking of the task the has privilege of running into that 
cgroup.
>
>> So we don't need a can_fork() check for now.
> Anyway, good breakdown. Could you please add it to the commit message
> too?

Yes, I can put that into the commit log.

Cheers,
Longman

> Regards,
> Michal


  reply	other threads:[~2023-04-04 13:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31 14:50 [PATCH 0/3] cgroup/cpuset: Fix CLONE_INTO_CGROUP problem & other issues Waiman Long
2023-03-31 14:50 ` [PATCH 1/3] cgroup/cpuset: Make cpuset_fork() handle CLONE_INTO_CGROUP properly Waiman Long
2023-04-03 16:55   ` Michal Koutný
2023-04-03 17:18     ` Waiman Long
2023-04-03 17:29       ` Waiman Long
2023-04-04  9:19       ` Michal Koutný
2023-04-04 13:52         ` Waiman Long [this message]
2023-04-04 17:26           ` Waiman Long
2023-04-06  2:51   ` kernel test robot
2023-04-06 12:17     ` Waiman Long
2023-04-06  9:45   ` Christian Brauner
2023-04-06 14:08     ` Waiman Long
2023-03-31 14:50 ` [PATCH 2/3] cgroup/cpuset: Make cpuset_attach_task() skip subpartitions CPUs for top_cpuset Waiman Long
2023-04-03 16:35   ` Michal Koutný
2023-03-31 14:50 ` [PATCH 3/3] cgroup/cpuset: Allow only one active attach operation per cpuset Waiman Long
2023-04-03 16:47   ` Michal Koutný
2023-04-03 17:41     ` Waiman Long
2023-04-04  9:07       ` Michal Koutný
2023-04-04 14:12         ` Waiman Long
2023-04-06  9:44   ` Christian Brauner
2023-04-07 15:30     ` Waiman Long
2023-04-09 11:46       ` Christian Brauner

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=a01585bc-03f8-e32c-ac46-99ac484a5e5d@redhat.com \
    --to=longman@redhat.com \
    --cc=brauner@kernel.org \
    --cc=cgroups@vger.kernel.org \
    --cc=dietmar.eggemann@arm.com \
    --cc=gscrivan@redhat.com \
    --cc=hannes@cmpxchg.org \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan.x@bytedance.com \
    --cc=mkoutny@suse.com \
    --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

all inboxes | Powered by JetHome®