sched/core: Fix NULL pointer access fault in sched_setaffinity() with non-SMP configs
authorWaiman Long <longman@redhat.com>
Sun, 15 Jan 2023 19:31:22 +0000 (14:31 -0500)
committerIngo Molnar <mingo@kernel.org>
Mon, 16 Jan 2023 09:07:25 +0000 (10:07 +0100)
commit5657c116783545fb49cd7004994c187128552b12
tree4d8906a3c05a5b56455deccd6008a126e157684c
parentda07d2f9c153e457e845d4dcfdd13568d71d18a4
sched/core: Fix NULL pointer access fault in sched_setaffinity() with non-SMP configs

The kernel commit 9a5418bc48ba ("sched/core: Use kfree_rcu() in
do_set_cpus_allowed()") introduces a bug for kernels built with non-SMP
configs. Calling sched_setaffinity() on such a uniprocessor kernel will
cause cpumask_copy() to be called with a NULL pointer leading to general
protection fault. This is not really a problem in real use cases as
there aren't that many uniprocessor kernel configs in use and calling
sched_setaffinity() on such a uniprocessor system doesn't make sense.

Fix this problem by making sure cpumask_copy() will not be called in
such a case.

Fixes: 9a5418bc48ba ("sched/core: Use kfree_rcu() in do_set_cpus_allowed()")
Reported-by: kernel test robot <yujie.liu@intel.com>
Signed-off-by: Waiman Long <longman@redhat.com>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Acked-by: Peter Zijlstra <peterz@infradead.org>
Link: https://lore.kernel.org/r/20230115193122.563036-1-longman@redhat.com
kernel/sched/core.c