public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Waiman Long <longman@redhat.com>
Cc: Ingo Molnar <mingo@redhat.com>,
	Juri Lelli <juri.lelli@redhat.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
	Daniel Bristot de Oliveira <bristot@redhat.com>,
	Valentin Schneider <vschneid@redhat.com>,
	Tejun Heo <tj@kernel.org>, Zefan Li <lizefan.x@bytedance.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Will Deacon <will@kernel.org>,
	linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Lai Jiangshan <jiangshanlai@gmail.com>
Subject: Re: [PATCH v6 3/5] sched: Enforce user requested affinity
Date: Wed, 31 Aug 2022 11:14:25 +0200	[thread overview]
Message-ID: <Yw8mcbgYThZGpMfN@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20220826010119.1265764-4-longman@redhat.com>

On Thu, Aug 25, 2022 at 09:01:17PM -0400, Waiman Long wrote:

> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> index ac2b103d69dc..1c2f548e5369 100644
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -2928,11 +2928,40 @@ static int __set_cpus_allowed_ptr_locked(struct task_struct *p,
>  static int __set_cpus_allowed_ptr(struct task_struct *p,
>  				  const struct cpumask *new_mask, u32 flags)
>  {
> +	struct cpumask *alloc_mask = NULL;
>  	struct rq_flags rf;
>  	struct rq *rq;
> +	int ret;
>  
>  	rq = task_rq_lock(p, &rf);
> -	return __set_cpus_allowed_ptr_locked(p, new_mask, flags, rq, &rf);
> +	if (p->user_cpus_ptr) {
> +
> +		/*
> +		 * A scratch cpumask is allocated on the percpu runqueues
> +		 * to enable additional masking with user_cpus_ptr. This
> +		 * cpumask, once allocated, will not be freed.
> +		 */
> +		if (unlikely(!rq->scratch_mask)) {
> +			alloc_mask = kmalloc(cpumask_size(), GFP_ATOMIC);

This -- absolutely not. You can't have allocations under a
raw_spinlock_t.

  reply	other threads:[~2022-08-31  9:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-26  1:01 [PATCH v6 0/5] sched: Persistent user requested affinity Waiman Long
2022-08-26  1:01 ` [PATCH v6 1/5] sched: Add __releases annotations to affine_move_task() Waiman Long
2022-08-26  1:01 ` [PATCH v6 2/5] sched: Use user_cpus_ptr for saving user provided cpumask in sched_setaffinity() Waiman Long
2022-08-31  9:12   ` Peter Zijlstra
2022-08-31 20:46     ` Waiman Long
2022-08-26  1:01 ` [PATCH v6 3/5] sched: Enforce user requested affinity Waiman Long
2022-08-31  9:14   ` Peter Zijlstra [this message]
2022-08-31  9:18   ` Peter Zijlstra
2022-08-31  9:21     ` Peter Zijlstra
2022-08-31 21:00       ` Waiman Long
2022-08-31 20:48     ` Waiman Long
2022-08-26  1:01 ` [PATCH v6 4/5] sched: Handle set_cpus_allowed_ptr() & sched_setaffinity() race Waiman Long
2022-08-31  9:26   ` Peter Zijlstra
2022-08-31 20:53     ` Waiman Long
2022-08-31  9:47   ` Peter Zijlstra
2022-08-31 20:56     ` Waiman Long
2022-08-26  1:01 ` [PATCH v6 5/5] sched: Fix sched_setaffinity() and fork/clone() race 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=Yw8mcbgYThZGpMfN@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=bristot@redhat.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=hannes@cmpxchg.org \
    --cc=jiangshanlai@gmail.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan.x@bytedance.com \
    --cc=longman@redhat.com \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=tj@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.com \
    --cc=will@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