From: Peter Zijlstra <peterz@infradead.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [patch 1/2] sched: Protect task->cpus_allowed access in sched_getaffinity()
Date: Wed, 09 Dec 2009 09:00:01 +0100 [thread overview]
Message-ID: <1260345601.5489.64.camel@laptop> (raw)
In-Reply-To: <20091208202026.769251187@linutronix.de>
On Tue, 2009-12-08 at 20:24 +0000, Thomas Gleixner wrote:
> plain text document attachment
> (sched-fix-sched-get-affinity-racy-access.patch)
> sched_getaffinity() is not protected against a concurrent modification
> of the tasks affinity.
>
> Serialize the access with task_rq_lock(task).
>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> ---
> kernel/sched.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> Index: linux-2.6-tip/kernel/sched.c
> ===================================================================
> --- linux-2.6-tip.orig/kernel/sched.c
> +++ linux-2.6-tip/kernel/sched.c
> @@ -6631,6 +6631,8 @@ SYSCALL_DEFINE3(sched_setaffinity, pid_t
> long sched_getaffinity(pid_t pid, struct cpumask *mask)
> {
> struct task_struct *p;
> + unsigned long flags;
> + struct rq *rq;
> int retval;
>
> get_online_cpus();
> @@ -6645,7 +6647,9 @@ long sched_getaffinity(pid_t pid, struct
> if (retval)
> goto out_unlock;
>
> + rq = task_rq_lock(p, &flags);
> cpumask_and(mask, &p->cpus_allowed, cpu_online_mask);
> + task_rq_unlock(rq, &flags);
>
> out_unlock:
> read_unlock(&tasklist_lock);
>
Hehe, I wrote the exact same patch last night :-)
Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
next prev parent reply other threads:[~2009-12-09 8:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-08 20:24 [patch 1/2] sched: Protect task->cpus_allowed access in sched_getaffinity() Thomas Gleixner
2009-12-09 8:00 ` Peter Zijlstra [this message]
2009-12-09 9:52 ` [tip:sched/urgent] " tip-bot for Thomas Gleixner
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=1260345601.5489.64.camel@laptop \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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