Patch "sched: access local runqueue directly in single_task_running" has been added to the 4.1-stable tree
Subsystems (2)
This is a note to let you know that I've just added the patch titled
sched: access local runqueue directly in single_task_running
to the 4.1-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
sched-access-local-runqueue-directly-in-single_task_running.patch
and it can be found in the queue-4.1 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.
Quoted 1 line
From
00cc1633816de8c95f337608a1ea64e228faf771Mon Sep 17 00:00:00 2001
From: Dominik Dingel <[email protected]>
Date: Fri, 18 Sep 2015 11:27:45 +0200
Subject: sched: access local runqueue directly in single_task_running
From: Dominik Dingel <[email protected]>
commit 00cc1633816de8c95f337608a1ea64e228faf771 upstream.
Commit 2ee507c47293 ("sched: Add function single_task_running to let a task check if it is the only task running on a cpu") referenced the current runqueue with the smp_processor_id. When CONFIG_DEBUG_PREEMPT is enabled, that is only allowed if preemption is disabled or the currrent task is bound to the local cpu (e.g. kernel worker).
With commit f78195129963 ("kvm: add halt_poll_ns module parameter") KVM calls single_task_running. If CONFIG_DEBUG_PREEMPT is enabled that generates a lot of kernel messages.
To avoid adding preemption in that cases, as it would limit the usefulness, we change single_task_running to access directly the cpu local runqueue.
--- kernel/sched/core.c | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-)
kernel/sched/core.c +11 -4
@@ -2358,13 +2358,20 @@ unsigned long nr_running(void)/* * Check if only the current task is running on the cpu. +* +* Caution: this function does not check that the caller has disabled +* preemption, thus the result might have a time-of-check-to-time-of-use +* race. The caller is responsible to use it correctly, for example: +* +* - from a non-preemptable section (of course) +* +* - from a thread that is bound to a single CPU +* +* - in a loop with very short iterations (e.g. a polling loop) */ bool single_task_running (void ) { -if (cpu_rq (smp_processor_id ())->nr_running ==1 ) -return true; -else -return false; +return raw_rq ()->nr_running ==1 ; }EXPORT_SYMBOL (single_task_running);
Patches currently in stable-queue which might be from [email protected] are
queue-4.1/sched-access-local-runqueue-directly-in-single_task_running.patch