sched/core: Always panic when scheduling in atomic context

Scheduling in atomic context is indicative of a serious problem that, although may not be immediately lethal, can lead to strange issues and eventually a panic. We should therefore panic the first time it's detected. Signed-off-by: Sultan Alsawaf <[email protected]> Signed-off-by: atndko <[email protected]>
Official-Ayrton990 · Jun 6, 2022 · 2c5530c · 2c5530c
1 parent 47f546f
commit 2c5530c
Showing 1 changed file with 1 addition and 8 deletions.
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
@@ -4191,14 +4191,7 @@ static noinline void __schedule_bug(struct task_struct *prev)
 		print_ip_sym(preempt_disable_ip);
 		pr_cont("\n");
 	}
-	if (panic_on_warn)
-		panic("scheduling while atomic\n");
-
-#ifdef CONFIG_PANIC_ON_SCHED_BUG
-	BUG();
-#endif
-	dump_stack();
-	add_taint(TAINT_WARN, LOCKDEP_STILL_OK);
+	panic("scheduling while atomic\n");
 }
 
 /*