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 2/5] sched: Use user_cpus_ptr for saving user provided cpumask in sched_setaffinity()
Date: Wed, 31 Aug 2022 11:12:23 +0200 [thread overview]
Message-ID: <Yw8l9zhKxgUM0ulc@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20220826010119.1265764-3-longman@redhat.com>
On Thu, Aug 25, 2022 at 09:01:16PM -0400, Waiman Long wrote:
> void relax_compatible_cpus_allowed_ptr(struct task_struct *p)
> {
> - struct cpumask *user_mask = p->user_cpus_ptr;
> - unsigned long flags;
> -
> /*
> - * Try to restore the old affinity mask. If this fails, then
> - * we free the mask explicitly to avoid it being inherited across
> - * a subsequent fork().
> + * Try to restore the old affinity mask with __sched_setaffinity().
> + * Cpuset masking will be done there too.
> */
> - if (!user_mask || !__sched_setaffinity(p, user_mask))
> - return;
> -
> - raw_spin_lock_irqsave(&p->pi_lock, flags);
> - user_mask = clear_user_cpus_ptr(p);
> - raw_spin_unlock_irqrestore(&p->pi_lock, flags);
> -
> - kfree(user_mask);
> + __sched_setaffinity(p, task_user_cpus(p), false);
> }
We have an issue with __sched_setaffinity() failing here. I'm not sure
ignoring the failure is the right thing -- but I'm also not enturely
sure what is.
> void set_task_cpu(struct task_struct *p, unsigned int new_cpu)
> @@ -8081,10 +8046,11 @@ int dl_task_check_affinity(struct task_struct *p, const struct cpumask *mask)
> #endif
>
> static int
> -__sched_setaffinity(struct task_struct *p, const struct cpumask *mask)
> +__sched_setaffinity(struct task_struct *p, const struct cpumask *mask, bool save_mask)
> {
> int retval;
> cpumask_var_t cpus_allowed, new_mask;
> + struct cpumask *user_mask = NULL;
>
> if (!alloc_cpumask_var(&cpus_allowed, GFP_KERNEL))
> return -ENOMEM;
> @@ -8100,8 +8066,22 @@ __sched_setaffinity(struct task_struct *p, const struct cpumask *mask)
> retval = dl_task_check_affinity(p, new_mask);
> if (retval)
> goto out_free_new_mask;
> +
> + /*
> + * Save the user requested mask internally now and then update
> + * user_cpus_ptr later after making sure this call will be
> + * successful, i.e. retval == 0.
> + */
> + if (save_mask) {
> + user_mask = kmalloc(cpumask_size(), GFP_KERNEL);
> + if (!user_mask) {
> + retval = -ENOMEM;
> + goto out_free_new_mask;
> + }
> + cpumask_copy(user_mask, mask);
> + }
> again:
> - retval = __set_cpus_allowed_ptr(p, new_mask, SCA_CHECK | SCA_USER);
> + retval = __set_cpus_allowed_ptr(p, new_mask, SCA_CHECK);
> if (retval)
> goto out_free_new_mask;
>
> @@ -8115,7 +8095,16 @@ __sched_setaffinity(struct task_struct *p, const struct cpumask *mask)
> goto again;
> }
>
> + if (save_mask) {
> + unsigned long flags;
> +
> + /* Use pi_lock to synchronize changes to user_cpus_ptr */
> + raw_spin_lock_irqsave(&p->pi_lock, flags);
> + swap(p->user_cpus_ptr, user_mask);
> + raw_spin_unlock_irqrestore(&p->pi_lock, flags);
> + }
> out_free_new_mask:
> + kfree(user_mask);
> free_cpumask_var(new_mask);
> out_free_cpus_allowed:
> free_cpumask_var(cpus_allowed);
I'm confused as to why it's put in this function and not in the one
caller that actually sets the new @save_mask true, here:
> @@ -8158,7 +8147,7 @@ long sched_setaffinity(pid_t pid, const struct cpumask *in_mask)
> if (retval)
> goto out_put_task;
>
> - retval = __sched_setaffinity(p, in_mask);
> + retval = __sched_setaffinity(p, in_mask, true);
> out_put_task:
> put_task_struct(p);
> return retval;
next prev parent reply other threads:[~2022-08-31 9:12 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 [this message]
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
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=Yw8l9zhKxgUM0ulc@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
all inboxes | Powered by JetHome®