[Android 5.15] BUG: soft lockup in bpf_prog_free_deferred

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 5d96939590c0 Revert "hrtimer: Report offline hrtimer enque..
git tree: android13-5.15-lts
console output: https://syzkaller.appspot.com/x/log.txt?x=13f943e8980000
kernel config: https://syzkaller.appspot.com/x/.config?x=8b088e4698b12339
dashboard link: https://syzkaller.appspot.com/bug?extid=cb1a5c14e7e68140e68d
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=125696a0980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=119b4fbb180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/854ff2d8dabc/disk-5d969395.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b499c380335f/vmlinux-5d969395.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4c9f082251f9/bzImage-5d969395.xz

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

watchdog: BUG: soft lockup - CPU#0 stuck for 246s! [kworker/0:4:844]
Modules linked in:
CPU: 0 PID: 844 Comm: kworker/0:4 Tainted: G W 5.15.149-syzkaller-00490-g5d96939590c0 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Workqueue: events bpf_prog_free_deferred
RIP: 0010:__sanitizer_cov_trace_pc+0x0/0x60 kernel/kcov.c:190
Code: 00 00 00 0f 0b 0f 1f 44 00 00 55 48 89 e5 53 48 89 fb e8 13 00 00 00 48 8b 3d 64 23 96 05 48 89 de e8 d4 5f 41 00 5b 5d c3 cc <55> 48 89 e5 48 8b 45 08 65 48 8b 0d 40 47 92 7e 65 8b 15 41 47 92
RSP: 0018:ffffc900009a7878 EFLAGS: 00000202
RAX: 0000000000000000 RBX: 1ffff1103ee276cd RCX: ffff88810bba13c0
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc900009a7988 R08: ffffffff8165816a R09: ffffc900009a77c0
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000001
R13: ffff8881f713b668 R14: ffff8881f7038280 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f5dd8fa701d CR3: 00000001063ba000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
</IRQ>
<TASK>
on_each_cpu_cond_mask+0x40/0x80 kernel/smp.c:1135
on_each_cpu include/linux/smp.h:71 [inline]
flush_tlb_kernel_range+0x49/0x210 arch/x86/mm/tlb.c:1026
__purge_vmap_area_lazy+0x230/0x1690 mm/vmalloc.c:1694
_vm_unmap_aliases+0x339/0x3b0 mm/vmalloc.c:2118
vm_remove_mappings mm/vmalloc.c:2611 [inline]
__vunmap+0x617/0x8f0 mm/vmalloc.c:2642
__vfree mm/vmalloc.c:2700 [inline]
vfree+0x7f/0xb0 mm/vmalloc.c:2731
module_memfree+0x17/0x30 kernel/module.c:2150
bpf_jit_free_exec+0x15/0x20 kernel/bpf/core.c:867
bpf_jit_binary_free kernel/bpf/core.c:914 [inline]
bpf_jit_free+0x98/0x240 kernel/bpf/core.c:927
bpf_prog_free_deferred+0x61e/0x730 kernel/bpf/core.c:2296
process_one_work+0x6bb/0xc10 kernel/workqueue.c:2325
worker_thread+0xad5/0x12a0 kernel/workqueue.c:2472
kthread+0x421/0x510 kernel/kthread.c:337
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</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

[syzbot]

Auto-closing this bug as obsolete.
No recent activity, existing reproducers are no longer triggering the issue.