Messages in this thread | | | Subject | Re: + work_on_cpu-rewrite-it-to-create-a-kernel-thread-on-demand.patch added to -mm tree | From | (Eric W. Biederman) | Date | Thu, 12 Feb 2009 14:08:09 -0800 |
| |
Andrew Morton <akpm@linux-foundation.org> writes:
> The problem with set_cpus_allowed() is that some other > suitably-privileged userspace process can come in from the side and > modify your cpus_allowed at any time.
According to the comments the only reason we care is so that we get the appropriate NUMA affinity by default. I don't think it would be fatal if userspace messed around and we had a wrong value.
Does work_on_cpu prevent that?
Eric
| |