[Android 5.15] BUG: soft lockup in sk_psock_destroy

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: ad06eaf051cd Merge branch 'android13-5.15' into branch 'an..
git tree: android13-5.15-lts
console output: https://syzkaller.appspot.com/x/log.txt?x=178edaf5180000
kernel config: https://syzkaller.appspot.com/x/.config?x=49ce29477ba81e8f
dashboard link: https://syzkaller.appspot.com/bug?extid=3399c87d5a1eca38285b
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=12844c3b180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17a267cb180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/11af0aa6a668/disk-ad06eaf0.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4402d93fba04/vmlinux-ad06eaf0.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f6d6b2b05230/bzImage-ad06eaf0.xz

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

watchdog: BUG: soft lockup - CPU#1 stuck for 225s! [kworker/1:0:744]
Modules linked in:
CPU: 1 PID: 744 Comm: kworker/1:0 Not tainted 5.15.148-syzkaller-00013-gad06eaf051cd #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Workqueue: events sk_psock_destroy

RIP: 0010:native_safe_halt arch/x86/include/asm/irqflags.h:51 [inline]
RIP: 0010:arch_safe_halt arch/x86/include/asm/irqflags.h:89 [inline]
RIP: 0010:kvm_wait+0x147/0x180 arch/x86/kernel/kvm.c:918
Code: 4c 89 e8 48 c1 e8 03 42 0f b6 04 20 84 c0 44 8b 74 24 1c 75 34 41 0f b6 45 00 44 38 f0 75 10 66 90 0f 00 2d 5b 03 f3 03 fb f4 <e9> 24 ff ff ff fb e9 1e ff ff ff 44 89 e9 80 e1 07 38 c1 7c a3 4c
RSP: 0018:ffffc90000997620 EFLAGS: 00000246

RAX: 0000000000000003 RBX: 1ffff92000132ec8 RCX: ffffffff8154f88f
RDX: dffffc0000000000 RSI: 0000000000000003 RDI: ffff88810a9fcad8
RBP: ffffc900009976d0 R08: dffffc0000000000 R09: ffffed102153f95c
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff88810a9fcad8 R14: 0000000000000003 R15: 1ffff92000132ecc
FS: 0000000000000000(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffd1b066618 CR3: 0000000105986000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
</IRQ>
<TASK>
pv_wait arch/x86/include/asm/paravirt.h:597 [inline]
pv_wait_head_or_lock kernel/locking/qspinlock_paravirt.h:470 [inline]
__pv_queued_spin_lock_slowpath+0x6bc/0xc40 kernel/locking/qspinlock.c:508
pv_queued_spin_lock_slowpath arch/x86/include/asm/paravirt.h:585 [inline]
queued_spin_lock_slowpath arch/x86/include/asm/qspinlock.h:51 [inline]
queued_spin_lock include/asm-generic/qspinlock.h:85 [inline]
do_raw_spin_lock include/linux/spinlock.h:187 [inline]
__raw_spin_lock_bh include/linux/spinlock_api_smp.h:136 [inline]
_raw_spin_lock_bh+0x139/0x1b0 kernel/locking/spinlock.c:178
sock_hash_delete_elem+0xb1/0x2f0 net/core/sock_map.c:937
bpf_prog_2c29ac5cdc6b1842+0x3a/0x2f8
bpf_dispatcher_nop_func include/linux/bpf.h:785 [inline]
__bpf_prog_run include/linux/filter.h:625 [inline]
bpf_prog_run include/linux/filter.h:632 [inline]
__bpf_trace_run kernel/trace/bpf_trace.c:1883 [inline]
bpf_trace_run2+0xec/0x210 kernel/trace/bpf_trace.c:1920
__bpf_trace_kfree+0x6f/0x90 include/trace/events/kmem.h:118
trace_kfree include/trace/events/kmem.h:118 [inline]
kfree+0x1f3/0x220 mm/slub.c:4569
sk_psock_free_link include/linux/skmsg.h:420 [inline]
sock_map_del_link net/core/sock_map.c:160 [inline]
sock_map_unref+0x352/0x4d0 net/core/sock_map.c:182
sock_hash_delete_elem+0x274/0x2f0 net/core/sock_map.c:941
bpf_prog_2c29ac5cdc6b1842+0x3a/0x2f8
bpf_dispatcher_nop_func include/linux/bpf.h:785 [inline]
__bpf_prog_run include/linux/filter.h:625 [inline]
bpf_prog_run include/linux/filter.h:632 [inline]
__bpf_trace_run kernel/trace/bpf_trace.c:1883 [inline]
bpf_trace_run2+0xec/0x210 kernel/trace/bpf_trace.c:1920
__bpf_trace_kfree+0x6f/0x90 include/trace/events/kmem.h:118
trace_kfree include/trace/events/kmem.h:118 [inline]
kfree+0x1f3/0x220 mm/slub.c:4569
sk_psock_destroy+0x43b/0x4a0 net/core/skmsg.c:829
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