Re: [PATCH] sched: CPU hotplug race vs. set_cpus_allowed()

* Kirill Korotaev <[email protected]> wrote:

> Looks like there is a race between set_cpus_allowed() and 
> move_task_off_dead_cpu(). __migrate_task() doesn't report any err 
> code, so task can be left on its runqueue if its cpus_allowed mask 
> changed so that dest_cpu is not longer a possible target. Also, 
> chaning cpus_allowed mask requires rq->lock being held.
> 
> Signed-Off-By: Kirill Korotaev <[email protected]>

good one!

Acked-by: Ingo Molnar <[email protected]>

	Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- [PATCH] sched: CPU hotplug race vs. set_cpus_allowed()
  - From: Kirill Korotaev <[email protected]>

Prev by Date: [PATCH] sched: CPU hotplug race vs. set_cpus_allowed()
Next by Date: Re: [PATCHSET] Announce: High-res timers, tickless/dyntick and dynamic HZ -V4
Previous by thread: [PATCH] sched: CPU hotplug race vs. set_cpus_allowed()
Next by thread: Re: [PATCH] sched: CPU hotplug race vs. set_cpus_allowed()
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]