[Android 5.10] BUG: soft lockup in smp_call_function

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 59b65efafe20 Revert "gpio: Allow per-parent interrupt data"
git tree: android13-5.10-lts
console+strace: https://syzkaller.appspot.com/x/log.txt?x=115f7c6aa80000
kernel config: https://syzkaller.appspot.com/x/.config?x=21b7341388eb4bd9
dashboard link: https://syzkaller.appspot.com/bug?extid=a47a3be3b3669f03dbd0
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=1211684aa80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13082152a80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/af0aa144141b/disk-59b65efa.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c90c9cff963e/vmlinux-59b65efa.xz
kernel image: https://storage.googleapis.com/syzbot-assets/81a3f67fcae6/bzImage-59b65efa.xz

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

watchdog: BUG: soft lockup - CPU#0 stuck for 123s! [kworker/u4:2:110]
Modules linked in:
CPU: 0 PID: 110 Comm: kworker/u4:2 Not tainted 5.10.186-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2023
Workqueue: events_unbound toggle_allocation_gate
RIP: 0010:csd_lock_wait kernel/smp.c:229 [inline]
RIP: 0010:smp_call_function_single+0x27d/0x510 kernel/smp.c:517
Code: 00 44 8b 6c 24 48 44 89 ee 83 e6 01 31 ff e8 ca e7 0a 00 41 83 e5 01 75 0a e8 0f e4 0a 00 e9 eb 00 00 00 f3 90 42 0f b6 04 23 <84> c0 75 15 f7 44 24 48 01 00 00 00 0f 84 cd 00 00 00 e8 ec e3 0a
RSP: 0018:ffffc90000c97720 EFLAGS: 00000293
RAX: 0000000000000000 RBX: 1ffff92000192eed RCX: ffff88810e52a780
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc90000c97810 R08: ffffffff815fa3c6 R09: ffffed103ee2aec9
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 0000000000000001 R14: ffffc90000c97768 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f04813789f8 CR3: 000000000660f000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
</IRQ>
smp_call_function_many_cond+0x94e/0xa30 kernel/smp.c:653
smp_call_function_many kernel/smp.c:716 [inline]
smp_call_function kernel/smp.c:738 [inline]
on_each_cpu+0xa8/0x1a0 kernel/smp.c:837
text_poke_sync arch/x86/kernel/alternative.c:1300 [inline]
text_poke_bp_batch+0x1d4/0x600 arch/x86/kernel/alternative.c:1491
text_poke_flush arch/x86/kernel/alternative.c:1659 [inline]
text_poke_finish+0x1a/0x30 arch/x86/kernel/alternative.c:1666
arch_jump_label_transform_apply+0x15/0x30 arch/x86/kernel/jump_label.c:126
__jump_label_update+0x36a/0x380 kernel/jump_label.c:459
jump_label_update+0x379/0x400 kernel/jump_label.c:825
static_key_enable_cpuslocked+0x12f/0x250 kernel/jump_label.c:177
static_key_enable+0x1a/0x30 kernel/jump_label.c:190
toggle_allocation_gate+0xbf/0x450 mm/kfence/core.c:624
process_one_work+0x6dc/0xbd0 kernel/workqueue.c:2298
worker_thread+0xaea/0x1510 kernel/workqueue.c:2444
kthread+0x34b/0x3d0 kernel/kthread.c:313
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:299


---
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 bug is already fixed, 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 change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

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

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