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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 8a1d809b0545 Linux 5.15.142
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=153fddfae80000
kernel config: https://syzkaller.appspot.com/x/.config?x=ee92f7141049e8f2
dashboard link: https://syzkaller.appspot.com/bug?extid=12eef28cd33986d05b97
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=150da9cae80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=173d015ce80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8965895d90e2/disk-8a1d809b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f8d2c2cd9799/vmlinux-8a1d809b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4fa328be23e7/bzImage-8a1d809b.xz

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

rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
(detected by 0, t=10502 jiffies, g=3489, q=17)
rcu: All QSes seen, last rcu_preempt kthread activity 10502 (4294966616-4294956114), jiffies_till_next_fqs=1, root ->qsmask 0x0
rcu: rcu_preempt kthread starved for 10502 jiffies! g3489 f0x2 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:27288 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:1884
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:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>
rcu: Stack dump where RCU GP kthread last ran:
NMI backtrace for cpu 0
CPU: 0 PID: 3549 Comm: syz-executor134 Not tainted 5.15.142-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
Call Trace:
<IRQ>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb 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_check_gp_kthread_starvation+0x1d2/0x240 kernel/rcu/tree_stall.h:487
print_other_cpu_stall+0x137a/0x14d0 kernel/rcu/tree_stall.h:592
check_cpu_stall kernel/rcu/tree_stall.h:745 [inline]
rcu_pending kernel/rcu/tree.c:3932 [inline]
rcu_sched_clock_irq+0xa38/0x1150 kernel/rcu/tree.c:2619
update_process_times+0x196/0x200 kernel/time/timer.c:1788
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:1685 [inline]
__hrtimer_run_queues+0x55b/0xcf0 kernel/time/hrtimer.c:1749
hrtimer_interrupt+0x392/0x980 kernel/time/hrtimer.c:1811
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:__syscall_enter_from_user_work kernel/entry/common.c:87 [inline]
RIP: 0010:syscall_enter_from_user_mode+0x37/0x230 kernel/entry/common.c:108
Code: 49 89 fe 48 8b 7c 24 30 e8 46 f6 ff ff e9 88 01 00 00 e9 8c 01 00 00 e8 07 b8 6a f7 e8 f2 b5 6a f7 fb 65 4c 8b 3d e9 7c e6 75 <49> 8b 6f 08 40 f6 c5 3f 0f 84 d6 00 00 00 40 f6 c5 20 74 17 4c 89
RSP: 0018:ffffc90002f37ef8 EFLAGS: 00000282
RAX: bc175e6d25de0b00 RBX: 0000000000000027 RCX: ffffffff913c6f03
RDX: dffffc0000000000 RSI: ffffffff8a8b0d60 RDI: ffffffff8ad87dc0
RBP: ffffc90002f37f48 R08: ffffffff8186a8f0 R09: fffffbfff1bc72d6
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000000
R13: 0000000000000000 R14: ffffc90002f37f58 R15: ffff8880208fd940
do_syscall_64+0x1e/0xb0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7fd4c3016387
Code: 0b e9 68 fe ff ff 48 83 c4 18 48 8d 3d 52 0f 09 00 5b 5d 41 5c 41 5d 41 5e 41 5f e9 63 d8 fd ff 0f 1f 00 b8 27 00 00 00 0f 05 <c3> 0f 1f 84 00 00 00 00 00 31 f6 31 ff e9 c7 e5 02 00 0f 1f 80 00
RSP: 002b:00007ffd33b213c8 EFLAGS: 00000202 ORIG_RAX: 0000000000000027
RAX: ffffffffffffffda RBX: 00007ffd33b21530 RCX: 00007fd4c3016387
RDX: 00007ffd33b21400 RSI: 00007ffd33b21530 RDI: 0000000000000021
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 0000555555827370
R13: 0000000000000002 R14: 00007ffd33b21a10 R15: 00007ffd33b21a00
</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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

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