[v5.15] INFO: rcu detected stall in irqentry_exit

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c61bd26ae81a Linux 5.15.160
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1610fa36980000
kernel config: https://syzkaller.appspot.com/x/.config?x=235f0e81ca937c17
dashboard link: https://syzkaller.appspot.com/bug?extid=9c94b6915471419d023e
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d61a97eef8b9/disk-c61bd26a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ab4908b4b59b/vmlinux-c61bd26a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d818fd46802b/bzImage-c61bd26a.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+9c94b6...@syzkaller.appspotmail.com

rcu: INFO: rcu_preempt self-detected stall on CPU
rcu: 1-...!: (10499 ticks this GP) idle=f79/1/0x4000000000000000 softirq=7368/7368 fqs=4
(t=10500 jiffies g=7581 q=22)
rcu: rcu_preempt kthread starved for 10491 jiffies! g7581 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=0
rcu: Unless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior.
rcu: RCU grace-period kthread stack dump:
task:rcu_preempt state:R running task stack:27000 pid: 15 ppid: 2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0x12c4/0x45b0 kernel/sched/core.c:6376
schedule+0x11b/0x1f0 kernel/sched/core.c:6459
schedule_timeout+0x1b9/0x300 kernel/time/timer.c:1914
rcu_gp_fqs_loop+0x2bf/0x1080 kernel/rcu/tree.c:1972
rcu_gp_kthread+0xa4/0x360 kernel/rcu/tree.c:2145
kthread+0x3f6/0x4f0 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:300
</TASK>
rcu: Stack dump where RCU GP kthread last ran:
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 3852 Comm: syz-executor.4 Not tainted 5.15.160-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
RIP: 0010:pid_nr_ns kernel/pid.c:478 [inline]
RIP: 0010:__task_pid_nr_ns+0x2a5/0x420 kernel/pid.c:500
Code: 89 c3 31 ff 89 c6 e8 5a d6 2b 00 85 db 0f 84 c9 00 00 00 80 3d e1 6e 7c 0c 01 0f 85 c6 00 00 00 e8 e0 d2 2b 00 e9 3e ff ff ff <e8> d6 d2 2b 00 49 8d 9c 1f d0 00 00 00 48 89 d8 48 c1 e8 03 42 0f
RSP: 0018:ffffc90003107ef8 EFLAGS: 00000246
RAX: 1ffff1100be16b35 RBX: 0000000000000010 RCX: 0000000000040000
RDX: ffff88801fd18000 RSI: 0000000000000001 RDI: 0000000000000001
RBP: ffff88805f0b59a8 R08: ffffffff81548969 R09: fffffbfff1f7f019
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 0000000000000000 R14: ffff888074606000 R15: ffff88805f0b58c0
FS: 00007f63e782e6c0(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f63e8de8000 CR3: 0000000062a56000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<TASK>
task_tgid_vnr include/linux/sched.h:1587 [inline]
__do_sys_getpid+0x19/0x20 kernel/sys.c:945
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f63e8cb26e7
Code: 0b e9 68 fe ff ff 48 83 c4 18 48 8d 3d 72 01 c7 00 5b 5d 41 5c 41 5d 41 5e 41 5f e9 d3 68 fd ff 0f 1f 00 b8 27 00 00 00 0f 05 <c3> 0f 1f 84 00 00 00 00 00 b8 66 00 00 00 0f 05 c3 0f 1f 84 00 00
RSP: 002b:00007f63e782db88 EFLAGS: 00000206 ORIG_RAX: 0000000000000027
RAX: ffffffffffffffda RBX: 00007f63e782dcf0 RCX: 00007f63e8cb26e7
RDX: 00007f63e782dbc0 RSI: 00007f63e782dcf0 RDI: 0000000000000021
RBP: 0000000000000000 R08: 00007f63e782e6c0 R09: 00007f63e782e6c0
R10: 0000000000000000 R11: 0000000000000206 R12: 00007f63e8debf8c
R13: 000000000000000b R14: 00007ffcab5a5440 R15: 00007ffcab5a5528
</TASK>
NMI backtrace for cpu 1
CPU: 1 PID: 20 Comm: ksoftirqd/1 Not tainted 5.15.160-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
Call Trace:
<IRQ>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2d0 lib/dump_stack.c:106
nmi_cpu_backtrace+0x46a/0x4a0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x181/0x2a0 lib/nmi_backtrace.c:62
trigger_single_cpu_backtrace include/linux/nmi.h:166 [inline]
rcu_dump_cpu_stacks+0x223/0x390 kernel/rcu/tree_stall.h:349
print_cpu_stall+0x320/0x600 kernel/rcu/tree_stall.h:633
check_cpu_stall kernel/rcu/tree_stall.h:727 [inline]
rcu_pending kernel/rcu/tree.c:3932 [inline]
rcu_sched_clock_irq+0x8d9/0x1150 kernel/rcu/tree.c:2619
update_process_times+0x196/0x200 kernel/time/timer.c:1818
tick_sched_handle kernel/time/tick-sched.c:254 [inline]
tick_sched_timer+0x386/0x550 kernel/time/tick-sched.c:1473
__run_hrtimer kernel/time/hrtimer.c:1686 [inline]
__hrtimer_run_queues+0x55b/0xcf0 kernel/time/hrtimer.c:1750
hrtimer_interrupt+0x392/0x980 kernel/time/hrtimer.c:1812
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1085 [inline]
__sysvec_apic_timer_interrupt+0x139/0x470 arch/x86/kernel/apic/apic.c:1102
sysvec_apic_timer_interrupt+0x8c/0xb0 arch/x86/kernel/apic/apic.c:1096
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:638
RIP: 0010:lock_is_held_type+0x137/0x180
Code: 75 40 48 c7 04 24 00 00 00 00 9c 8f 04 24 f7 04 24 00 02 00 00 75 46 41 f7 c4 00 02 00 00 74 01 fb 65 48 8b 04 25 28 00 00 00 <48> 3b 44 24 08 75 3c 89 e8 48 83 c4 10 5b 41 5c 41 5d 41 5e 41 5f
RSP: 0018:ffffc90000da7a98 EFLAGS: 00000206
RAX: cc17a4b851a4e500 RBX: ffffc90000da0000 RCX: ffff888012a10000
RDX: 0000000000000010 RSI: ffffffff8a8b3c20 RDI: ffffffff8ad8f6c0
RBP: 0000000000000000 R08: dffffc0000000000 R09: ffffc90000da7c40
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000246
R13: ffff888012a10000 R14: 00000000ffffffff R15: ffffffff8c91fa60
lock_is_held include/linux/lockdep.h:287 [inline]
schedule_debug kernel/sched/core.c:5602 [inline]
__schedule+0x202/0x45b0 kernel/sched/core.c:6267
preempt_schedule_irq+0xf7/0x1c0 kernel/sched/core.c:6780
irqentry_exit+0x53/0x80 kernel/entry/common.c:432
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:638
RIP: 0010:schedule+0x10a/0x1f0 kernel/sched/core.c:6458
Code: a3 f7 49 8b 07 4c 39 f8 74 0d 4c 89 f7 be 01 00 00 00 e8 89 d0 c6 f9 4c 89 eb 48 c1 eb 03 eb 0a 49 f7 45 00 08 00 00 00 74 39 <bf> 01 00 00 00 e8 7c 30 31 f7 31 ff e8 35 b9 ff ff bf 01 00 00 00
RSP: 0018:ffffc90000da7e40 EFLAGS: 00000202
RAX: 0000000000000001 RBX: 1ffff11002542000 RCX: ffffffff8a263012
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffff888012a10000
RBP: ffff888012a11780 R08: dffffc0000000000 R09: ffffed1002542001
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff888012a10000 R14: 0000000000000000 R15: 1ffff110023bacac
smpboot_thread_fn+0x599/0x9d0 kernel/smpboot.c:160
kthread+0x3f6/0x4f0 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:300
</TASK>


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup