[v6.1] INFO: rcu detected stall in process_one_work

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 38fb82ecd144 Linux 6.1.71
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11a15deee80000
kernel config: https://syzkaller.appspot.com/x/.config?x=f8d4b3f2bd71350c
dashboard link: https://syzkaller.appspot.com/bug?extid=91c2d7e0b70368b7f8f4
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=127fa4fee80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12031f5ee80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/44a009057e6d/disk-38fb82ec.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ef84f309ccb4/vmlinux-38fb82ec.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c351b9cee4f7/bzImage-38fb82ec.xz

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

rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: 1-...!: (1 GPs behind) idle=6b1c/1/0x4000000000000000 softirq=6948/6954 fqs=0
(detected by 0, t=10506 jiffies, g=4777, q=51 ncpus=2)
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 27 Comm: kworker/1:1 Not tainted 6.1.71-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
Workqueue: events_freezable_power_ sync_hw_clock
RIP: 0010:validate_chain+0x5ed/0x5950 kernel/locking/lockdep.c:3837
Code: 01 00 00 0e 36 e0 45 49 c7 04 04 00 00 00 00 49 c7 44 04 09 00 00 00 00 49 c7 44 04 17 00 00 00 00 49 c7 44 04 23 00 00 00 00 <41> c6 44 04 2b 00 65 48 8b 04 25 28 00 00 00 48 3b 84 24 60 02 00
RSP: 0018:ffffc900001e07c0 EFLAGS: 00000002
RAX: 1ffff9200003c118 RBX: 00000000000a402b RCX: 1ffff9200003c118
RDX: 0000000000000001 RSI: ffff888013e66448 RDI: ffff888013e65940
RBP: ffffc900001e0a70 R08: dffffc0000000000 R09: fffffbfff2092045
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff888013e66468 R14: 0000000000000001 R15: 1ffff110027ccc8d
FS: 0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000600 CR3: 0000000079642000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<IRQ>
__lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5049
lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5662
rcu_lock_acquire include/linux/rcupdate.h:306 [inline]
rcu_read_lock include/linux/rcupdate.h:747 [inline]
advance_sched+0x6ec/0x970 net/sched/sch_taprio.c:753
__run_hrtimer kernel/time/hrtimer.c:1685 [inline]
__hrtimer_run_queues+0x5e5/0xe50 kernel/time/hrtimer.c:1749
hrtimer_interrupt+0x392/0x980 kernel/time/hrtimer.c:1811
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1095 [inline]
__sysvec_apic_timer_interrupt+0x156/0x580 arch/x86/kernel/apic/apic.c:1112
sysvec_apic_timer_interrupt+0x8c/0xb0 arch/x86/kernel/apic/apic.c:1106
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:653
RIP: 0010:lock_acquire+0x26f/0x5a0 kernel/locking/lockdep.c:5666
Code: 2b 00 74 08 4c 89 f7 e8 1f a4 77 00 f6 44 24 61 02 0f 85 84 01 00 00 41 f7 c7 00 02 00 00 74 01 fb 48 c7 44 24 40 0e 36 e0 45 <4b> c7 44 25 00 00 00 00 00 43 c7 44 25 09 00 00 00 00 43 c7 44 25
RSP: 0018:ffffc90000a3fb00 EFLAGS: 00000206
RAX: 0000000000000001 RBX: 1ffff92000147f6c RCX: ffffffff91c88103
RDX: dffffc0000000000 RSI: ffffffff8aebf840 RDI: ffffffff8b3cf940
RBP: ffffc90000a3fc48 R08: 1ffffffff20a1cbc R09: 000000000000ef33
R10: 00000000001310cd R11: dffffc0000000001 R12: 1ffff92000147f68
R13: dffffc0000000000 R14: ffffc90000a3fb60 R15: 0000000000000246
process_one_work+0x7bf/0x11d0 kernel/workqueue.c:2267
worker_thread+0xa47/0x1200 kernel/workqueue.c:2439
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 1.788 msecs
rcu: rcu_preempt kthread starved for 10506 jiffies! g4777 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:25528 pid:16 ppid:2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x142d/0x4550 kernel/sched/core.c:6558
schedule+0xbf/0x180 kernel/sched/core.c:6634
schedule_timeout+0x1b9/0x300 kernel/time/timer.c:1935
rcu_gp_fqs_loop+0x2d2/0x1120 kernel/rcu/tree.c:1674
rcu_gp_kthread+0xa3/0x3a0 kernel/rcu/tree.c:1873
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
rcu: Stack dump where RCU GP kthread last ran:
CPU: 0 PID: 51 Comm: kworker/u4:3 Not tainted 6.1.71-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
Workqueue: events_unbound toggle_allocation_gate
RIP: 0010:csd_lock_wait kernel/smp.c:424 [inline]
RIP: 0010:smp_call_function_many_cond+0x1fb9/0x3460 kernel/smp.c:998
Code: e8 0c 43 0b 00 41 83 e5 01 49 bd 00 00 00 00 00 fc ff df 75 0a e8 97 3f 0b 00 e9 1b ff ff ff f3 90 42 0f b6 04 2b 84 c0 75 14 <41> f7 07 01 00 00 00 0f 84 fe fe ff ff e8 75 3f 0b 00 eb e1 44 89
RSP: 0018:ffffc90000bc75a0 EFLAGS: 00000246
RAX: 0000000000000000 RBX: 1ffff11017328031 RCX: ffff8880176a3b80
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc90000bc7980 R08: ffffffff817f5554 R09: fffffbfff2092045
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000800000000
R13: dffffc0000000000 R14: 0000000000000001 R15: ffff8880b9940188
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f04d1b423c0 CR3: 000000000ce8e000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
</IRQ>
<TASK>
on_each_cpu_cond_mask+0x3b/0x80 kernel/smp.c:1166
on_each_cpu include/linux/smp.h:71 [inline]
text_poke_sync arch/x86/kernel/alternative.c:1329 [inline]
text_poke_bp_batch+0x2bb/0x940 arch/x86/kernel/alternative.c:1529
text_poke_flush arch/x86/kernel/alternative.c:1720 [inline]
text_poke_finish+0x16/0x30 arch/x86/kernel/alternative.c:1727
arch_jump_label_transform_apply+0x13/0x20 arch/x86/kernel/jump_label.c:146
static_key_enable_cpuslocked+0x12e/0x250 kernel/jump_label.c:177
static_key_enable+0x16/0x20 kernel/jump_label.c:190
toggle_allocation_gate+0xbf/0x480 mm/kfence/core.c:804
process_one_work+0x8a9/0x11d0 kernel/workqueue.c:2292
worker_thread+0xa47/0x1200 kernel/workqueue.c:2439
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</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