diff options
author | 2023-09-15 13:44:44 -0400 | |
---|---|---|
committer | 2023-09-19 10:48:04 +0200 | |
commit | cff9b2332ab762b7e0586c793c431a8f2ea4db04 (patch) | |
tree | 47b44aeadbfd968e701dea725ac1b026982f32e4 /drivers/net/ethernet/intel/igc | |
parent | Linux 6.6-rc2 (diff) | |
download | linux-cff9b2332ab762b7e0586c793c431a8f2ea4db04.tar.gz linux-cff9b2332ab762b7e0586c793c431a8f2ea4db04.tar.bz2 linux-cff9b2332ab762b7e0586c793c431a8f2ea4db04.zip |
kernel/sched: Modify initial boot task idle setup
Initial booting is setting the task flag to idle (PF_IDLE) by the call
path sched_init() -> init_idle(). Having the task idle and calling
call_rcu() in kernel/rcu/tiny.c means that TIF_NEED_RESCHED will be
set. Subsequent calls to any cond_resched() will enable IRQs,
potentially earlier than the IRQ setup has completed. Recent changes
have caused just this scenario and IRQs have been enabled early.
This causes a warning later in start_kernel() as interrupts are enabled
before they are fully set up.
Fix this issue by setting the PF_IDLE flag later in the boot sequence.
Although the boot task was marked as idle since (at least) d80e4fda576d,
I am not sure that it is wrong to do so. The forced context-switch on
idle task was introduced in the tiny_rcu update, so I'm going to claim
this fixes 5f6130fa52ee.
Fixes: 5f6130fa52ee ("tiny_rcu: Directly force QS when call_rcu_[bh|sched]() on idle_task")
Signed-off-by: Liam R. Howlett <Liam.Howlett@oracle.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Cc: stable@vger.kernel.org
Link: https://lore.kernel.org/linux-mm/CAMuHMdWpvpWoDa=Ox-do92czYRvkok6_x6pYUH+ZouMcJbXy+Q@mail.gmail.com/
Diffstat (limited to 'drivers/net/ethernet/intel/igc')
0 files changed, 0 insertions, 0 deletions