[Android 5.4] BUG: soft lockup in smp_call_function (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 4d7b888b5774 Merge "Merge tag 'android12-5.4.265_r00' into..
git tree: android12-5.4
console+strace: https://syzkaller.appspot.com/x/log.txt?x=178139a7e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=a2dd4b5d39d9fde5
dashboard link: https://syzkaller.appspot.com/bug?extid=1c28af2c1ffa3d34f12e
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=12ba8987e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=108204dfe80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/5e5c9fa42329/disk-4d7b888b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ac275030fbe9/vmlinux-4d7b888b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4855e16954a0/bzImage-4d7b888b.xz

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

kthread+0x2da/0x360 kernel/kthread.c:288
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:354
watchdog: BUG: soft lockup - CPU#1 stuck for 123s! [kworker/u4:2:179]
Modules linked in:
CPU: 1 PID: 179 Comm: kworker/u4:2 Not tainted 5.4.265-syzkaller-00033-g4d7b888b5774 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
Workqueue: events_unbound toggle_allocation_gate
RIP: 0010:__read_once_size include/linux/compiler.h:268 [inline]
RIP: 0010:csd_lock_wait kernel/smp.c:109 [inline]
RIP: 0010:smp_call_function_single+0x235/0x4a0 kernel/smp.c:311
Code: 0f 85 df 01 00 00 44 8b 74 24 58 44 89 f6 83 e6 01 31 ff e8 6d b0 0a 00 41 83 e6 01 75 0a e8 72 ad 0a 00 e9 f4 00 00 00 f3 90 <42> 0f b6 04 2b 84 c0 75 15 f7 44 24 58 01 00 00 00 0f 84 d6 00 00
RSP: 0018:ffff8881e4db78a0 EFLAGS: 00000293 ORIG_RAX: ffffffffffffff13
RAX: ffffffff81599971 RBX: 1ffff1103c9b6f1f RCX: ffff8881e9acaf40
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffff8881e4db7990 R08: ffffffff81599943 R09: ffffed103edcb189
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff1103c9b6f18
R13: dffffc0000000000 R14: 0000000000000001 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8881f6f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000090 CR3: 00000001dc048000 CR4: 00000000003406a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
</IRQ>
smp_call_function_many+0x6fe/0x9b0 kernel/smp.c:451
smp_call_function kernel/smp.c:509 [inline]
on_each_cpu+0xa5/0x1a0 kernel/smp.c:616
text_poke_bp_batch+0x11a/0x2b0 arch/x86/kernel/alternative.c:1038
arch_jump_label_transform_apply+0x27/0x40 arch/x86/kernel/jump_label.c:167
static_key_enable_cpuslocked+0x12c/0x240 kernel/jump_label.c:177
static_key_enable+0x16/0x20 kernel/jump_label.c:190
toggle_allocation_gate+0xb1/0x240 mm/kfence/core.c:624
process_one_work+0x765/0xd20 kernel/workqueue.c:2290
worker_thread+0xaef/0x1470 kernel/workqueue.c:2436
kthread+0x2da/0x360 kernel/kthread.c:288
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:354


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