[Android 5.15] BUG: soft lockup in syscall_exit_to_user_mode

[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=17f0c31a980000
kernel config: https://syzkaller.appspot.com/x/.config?x=8b088e4698b12339
dashboard link: https://syzkaller.appspot.com/bug?extid=190d662da0b79bb11eee
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=14f3cda4980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12868fdc980000

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+190d66...@syzkaller.appspotmail.com

watchdog: BUG: soft lockup - CPU#0 stuck for 246s! [syz-executor569:640]
Modules linked in:
CPU: 0 PID: 640 Comm: syz-executor569 Not tainted 5.15.149-syzkaller-00490-g5d96939590c0 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
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:ffffc90000a76f40 EFLAGS: 00000246
RAX: 0000000000000001 RBX: 1ffff9200014edec RCX: 1ffffffff0d1aa9c
RDX: 0000000000000001 RSI: 0000000000000001 RDI: ffff8881f7037ed4
RBP: ffffc90000a76ff0 R08: dffffc0000000000 R09: ffffed103ee06fdb
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff8881f7037ed4 R14: 0000000000000001 R15: 1ffff9200014edf0
FS: 0000000000000000(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f9489cbceb8 CR3: 000000011f72f000 CR4: 00000000003506b0
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_node kernel/locking/qspinlock_paravirt.h:325 [inline]
__pv_queued_spin_lock_slowpath+0x41b/0xc40 kernel/locking/qspinlock.c:473
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_map_delete net/core/sock_map.c:416 [inline]
sock_map_delete_elem+0x99/0x130 net/core/sock_map.c:448
bpf_prog_8a405b5ced52e191+0x42/0x1bc
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_run4+0x13f/0x270 kernel/trace/bpf_trace.c:1922
__bpf_trace_mm_page_alloc+0xbf/0xf0 include/trace/events/kmem.h:201
__traceiter_mm_page_alloc+0x3a/0x60 include/trace/events/kmem.h:201
trace_mm_page_alloc include/trace/events/kmem.h:201 [inline]
__alloc_pages+0x3cb/0x8f0 mm/page_alloc.c:5798
__alloc_pages_node include/linux/gfp.h:591 [inline]
alloc_pages_node include/linux/gfp.h:605 [inline]
alloc_pages include/linux/gfp.h:618 [inline]
__get_free_pages+0x10/0x30 mm/page_alloc.c:5813
tlb_next_batch mm/mmu_gather.c:29 [inline]
__tlb_remove_page_size+0x178/0x300 mm/mmu_gather.c:83
__tlb_remove_page include/asm-generic/tlb.h:444 [inline]
zap_pte_range mm/memory.c:1435 [inline]
zap_pmd_range mm/memory.c:1553 [inline]
zap_pud_range mm/memory.c:1582 [inline]
zap_p4d_range mm/memory.c:1603 [inline]
unmap_page_range+0x120a/0x1ca0 mm/memory.c:1624
unmap_single_vma mm/memory.c:1669 [inline]
unmap_vmas+0x389/0x560 mm/memory.c:1701
exit_mmap+0x3d8/0x6f0 mm/mmap.c:3209
__mmput+0x95/0x310 kernel/fork.c:1179
mmput+0x5b/0x170 kernel/fork.c:1202
exit_mm kernel/exit.c:552 [inline]
do_exit+0xb9c/0x2ca0 kernel/exit.c:865
do_group_exit+0x141/0x310 kernel/exit.c:1000
get_signal+0x7a3/0x1630 kernel/signal.c:2896
arch_do_signal_or_restart+0xbd/0x1680 arch/x86/kernel/signal.c:867
handle_signal_work kernel/entry/common.c:148 [inline]
exit_to_user_mode_loop+0xa0/0xe0 kernel/entry/common.c:172
exit_to_user_mode_prepare+0x5a/0xa0 kernel/entry/common.c:208
__syscall_exit_to_user_mode_work kernel/entry/common.c:290 [inline]
syscall_exit_to_user_mode+0x26/0x160 kernel/entry/common.c:301
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f9489c66859
Code: Unable to access opcode bytes at RIP 0x7f9489c6682f.
RSP: 002b:00007f9489c27228 EFLAGS: 00000246
ORIG_RAX: 00000000000000ca
RAX: 0000000000000001 RBX: 00007f9489cf0328 RCX: 00007f9489c66859
RDX: 00000000000f4240 RSI: 0000000000000081 RDI: 00007f9489cf032c
RBP: 00007f9489cf0320 R08: 00007f9489c276c0 R09: 00007f9489c276c0
R10: 00007f9489c276c0 R11: 0000000000000246 R12: 00007f9489cbd074
R13: 00636f6c6c615f65 R14: 5f656761705f6d6d R15: 00007ffecd85e6f8
</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.