Commit e7097e8b authored Oct 29, 2014 by Peter Zijlstra Committed by Ingo Molnar Nov 04, 2014

sched: Use WARN_ONCE for the might_sleep() TASK_RUNNING test



In some cases this can trigger a true flood of output.

Requested-by: Ingo Molnar <mingo@kernel.org>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Ingo Molnar <mingo@kernel.org>

parent ff960a73

kernel/sched/core.c

+1 −1

Original line number	Diff line number	Diff line
		@@ -7301,7 +7301,7 @@ void __might_sleep(const char *file, int line, int preempt_offset)
		* since we will exit with TASK_RUNNING make sure we enter with it,
		* otherwise we will destroy state.
		*/
		if (WARN(current->state != TASK_RUNNING,
		if (WARN_ONCE(current->state != TASK_RUNNING,
		"do not call blocking ops when !TASK_RUNNING; "
		"state=%lx set at [<%p>] %pS\n",
		current->state,