Commit e7097e8b authored by Peter Zijlstra's avatar Peter Zijlstra Committed by Ingo Molnar

sched: Use WARN_ONCE for the might_sleep() TASK_RUNNING test

In some cases this can trigger a true flood of output.
Requested-by: default avatarIngo Molnar <mingo@kernel.org>
Signed-off-by: default avatarPeter Zijlstra (Intel) <peterz@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: default avatarIngo Molnar <mingo@kernel.org>
parent ff960a73
...@@ -7301,7 +7301,7 @@ void __might_sleep(const char *file, int line, int preempt_offset) ...@@ -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, * since we will exit with TASK_RUNNING make sure we enter with it,
* otherwise we will destroy state. * 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; " "do not call blocking ops when !TASK_RUNNING; "
"state=%lx set at [<%p>] %pS\n", "state=%lx set at [<%p>] %pS\n",
current->state, current->state,
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment