Great! I'm glad someone is looking into this. Didn't look at
your patch too closely, but one obvious issue comes to mind.
How does the caller of set_cpus_allowed() lock down the specified
task so that set_cpus_allowed() can be sure it is still valid?
Obviously, this only becomes an issue when you open up the
routine to tasks other than 'current' as you have done. Do you
want to do task validation within set_cpus_allowed() with the
-- Mike - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/