[v5.15] INFO: rcu detected stall in clone3 (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3330a8d33e08 Linux 5.15.201
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1459d55a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=353ae28c40b35af5
dashboard link: https://syzkaller.appspot.com/bug?extid=ea4ad5aa0d82fee4b59b
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b65fe19af112/disk-3330a8d3.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/351948519a0d/vmlinux-3330a8d3.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a3b3f8477595/bzImage-3330a8d3.xz

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

rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: Tasks blocked on level-0 rcu_node (CPUs 0-1): P4319/1:b..l
(detected by 1, t=10502 jiffies, g=7141, q=642)
task:syz.1.12 state:R running task stack:26352 pid: 4319 ppid: 4184 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5049 [inline]
__schedule+0x11ef/0x43c0 kernel/sched/core.c:6395
preempt_schedule_irq+0xbb/0x160 kernel/sched/core.c:6799
irqentry_exit+0x63/0x70 kernel/entry/common.c:432
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:676
RIP: 0010:lock_is_held_type+0x13a/0x190 kernel/locking/lockdep.c:5671
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 c5 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:ffffc9000318f970 EFLAGS: 00000206
RAX: 4501dc9a69365500 RBX: ffff88807ea71dc0 RCX: 4501dc9a69365500
RDX: 0000000000000000 RSI: ffffffff8a2b3a20 RDI: ffffffff8a79f800
RBP: 0000000000000001 R08: dffffc0000000000 R09: 1ffffffff203a618
R10: dffffc0000000000 R11: fffffbfff203a619 R12: 0000000000000000
R13: 0000000000000246 R14: ffffffff8c31eaa0 R15: ffff88807ea728b0
copy_namespaces+0x10e/0x3e0 kernel/nsproxy.c:154
copy_process+0x1834/0x3e20 kernel/fork.c:2293
kernel_clone+0x23f/0x990 kernel/fork.c:2679
__do_sys_clone3 kernel/fork.c:2954 [inline]
__se_sys_clone3+0x312/0x3d0 kernel/fork.c:2938
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f96dd0c3589
RSP: 002b:00007fff7a0f4a98 EFLAGS: 00000202 ORIG_RAX: 00000000000001b3
RAX: ffffffffffffffda RBX: 00007f96dd07eb20 RCX: 00007f96dd0c3589
RDX: 00007f96dd07eb20 RSI: 0000000000000058 RDI: 00007fff7a0f4af0
RBP: 00007f96daeb76c0 R08: 00007f96daeb76c0 R09: 00007fff7a0f4bd7
R10: 0000000000000008 R11: 0000000000000202 R12: ffffffffffffffe8
R13: 000000000000006e R14: 00007fff7a0f4af0 R15: 00007fff7a0f4bd8
</TASK>
rcu: rcu_preempt kthread starved for 8835 jiffies! g7141 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:27760 pid: 15 ppid: 2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5049 [inline]
__schedule+0x11ef/0x43c0 kernel/sched/core.c:6395
schedule+0x11b/0x1e0 kernel/sched/core.c:6478
schedule_timeout+0x184/0x2d0 kernel/time/timer.c:2117
rcu_gp_fqs_loop+0x2be/0x11d0 kernel/rcu/tree.c:1972
rcu_gp_kthread+0x9b/0x370 kernel/rcu/tree.c:2145
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
rcu: Stack dump where RCU GP kthread last ran:
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0 skipped: idling at native_safe_halt arch/x86/include/asm/irqflags.h:51 [inline]
NMI backtrace for cpu 0 skipped: idling at arch_safe_halt arch/x86/include/asm/irqflags.h:89 [inline]
NMI backtrace for cpu 0 skipped: idling at default_idle+0xb/0x10 arch/x86/kernel/process.c:729


---
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