Messages in this thread Patch in this message | | | Date | Fri, 31 Oct 2014 12:10:44 +0100 | From | Peter Zijlstra <> | Subject | [PATCH 7/7] 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> --- kernel/sched/core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
--- a/kernel/sched/core.c +++ b/kernel/sched/core.c @@ -7301,7 +7301,7 @@ void __might_sleep(const char *file, int * 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,
| |