[Android 5.10] BUG: soft lockup in sock_close

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: e7daca75b4c3 ANDROID: GKI: db845c: Update symbols list and..
git tree: android13-5.10-lts
console output: https://syzkaller.appspot.com/x/log.txt?x=1361b24e180000
kernel config: https://syzkaller.appspot.com/x/.config?x=1a6e39f6bdc97aed
dashboard link: https://syzkaller.appspot.com/bug?extid=8e44f6baf770f194eef0
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=10f5b481180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15f1827e180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/cec0e413e034/disk-e7daca75.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e97d4453b5ff/vmlinux-e7daca75.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3d97ddfb5394/bzImage-e7daca75.xz

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

watchdog: BUG: soft lockup - CPU#0 stuck for 123s! [syz-executor376:1620]
Modules linked in:
CPU: 0 PID: 1620 Comm: syz-executor376 Not tainted 5.10.209-syzkaller-00001-ge7daca75b4c3 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024
RIP: 0010:native_restore_fl arch/x86/include/asm/irqflags.h:41 [inline]
RIP: 0010:arch_local_irq_restore arch/x86/include/asm/irqflags.h:84 [inline]
RIP: 0010:kvm_wait+0xfc/0x150 arch/x86/kernel/kvm.c:926
Code: 38 f0 75 26 41 f7 c7 00 02 00 00 75 0f 0f 1f 44 00 00 0f 00 2d 55 4c d5 03 f4 eb 0e 0f 1f 44 00 00 0f 00 2d 46 4c d5 03 fb f4 <4c> 89 7c 24 18 ff 74 24 18 9d 48 c7 44 24 20 0e 36 e0 45 49 c7 04
RSP: 0018:ffffc900025679e0 EFLAGS: 00000246
RAX: 0000000000000003 RBX: 1ffff920004acf40 RCX: ffffffff8150b554
RDX: 0000000000000001 RSI: 0000000000000003 RDI: ffffc90002567a20
RBP: ffffc90002567a90 R08: dffffc0000000000 R09: ffffed1022073c72
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff88811039e388 R14: 0000000000000003 R15: 0000000000000246
FS: 0000555556f2e3c0(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000002001f000 CR3: 000000010fc50000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
</IRQ>
pv_wait arch/x86/include/asm/paravirt.h:564 [inline]
pv_wait_head_or_lock kernel/locking/qspinlock_paravirt.h:470 [inline]
__pv_queued_spin_lock_slowpath+0x72f/0xc70 kernel/locking/qspinlock.c:508
pv_queued_spin_lock_slowpath arch/x86/include/asm/paravirt.h:554 [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:183 [inline]
__raw_spin_lock_bh include/linux/spinlock_api_smp.h:136 [inline]
_raw_spin_lock_bh+0x139/0x1b0 kernel/locking/spinlock.c:175
spin_lock_bh include/linux/spinlock.h:359 [inline]
lock_sock_nested+0x92/0x300 net/core/sock.c:3105
lock_sock include/net/sock.h:1640 [inline]
tipc_release+0x57/0x1440 net/tipc/socket.c:626
__sock_release net/socket.c:597 [inline]
sock_close+0xdf/0x270 net/socket.c:1286
__fput+0x309/0x760 fs/file_table.c:281
____fput+0x15/0x20 fs/file_table.c:314
task_work_run+0x129/0x190 kernel/task_work.c:164
tracehook_notify_resume include/linux/tracehook.h:188 [inline]
exit_to_user_mode_loop+0xbf/0xd0 kernel/entry/common.c:172
exit_to_user_mode_prepare kernel/entry/common.c:199 [inline]
syscall_exit_to_user_mode+0xc5/0x1d0 kernel/entry/common.c:274
do_syscall_64+0x40/0x70 arch/x86/entry/common.c:56
entry_SYSCALL_64_after_hwframe+0x61/0xc6
RIP: 0033:0x7fdc3012ec7a
Code: 48 3d 00 f0 ff ff 77 48 c3 0f 1f 80 00 00 00 00 48 83 ec 18 89 7c 24 0c e8 c3 69 02 00 8b 7c 24 0c 89 c2 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 36 89 d7 89 44 24 0c e8 23 6a 02 00 8b 44 24
RSP: 002b:00007fff154cb820 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000005 RCX: 00007fdc3012ec7a
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000004
RBP: 000000000004ce93 R08: 0000000000000000 R09: 00007fff154cb8f0
R10: 0000000000000000 R11: 0000000000000293 R12: 00007fdc301bc40c
R13: 00007fff154cb880 R14: 00007fff154cb8f0 R15: 00007fdc300fa200


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

Hello,

syzbot found the following issue on:

HEAD commit: 993bed180178 Merge "Merge branch 'android13-5.15' into bra..
git tree: android13-5.15-lts
console+strace: https://syzkaller.appspot.com/x/log.txt?x=117a22a5180000
kernel config: https://syzkaller.appspot.com/x/.config?x=49ce29477ba81e8f
dashboard link: https://syzkaller.appspot.com/bug?extid=62469057aed52ef281ed

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=14710b91180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16739546180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/803c31a2cd6a/disk-993bed18.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fb3ff89c92a4/vmlinux-993bed18.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b0859874279b/bzImage-993bed18.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:

Reported-by: syzbot+624690...@syzkaller.appspotmail.com

RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: ffffffffffffffb0
R13: 00007f02e603a320 R14: 00007f02e603a32c R15: 00007f02e6007064
</TASK>
watchdog: BUG: soft lockup - CPU#1 stuck for 226s! [syz-executor330:5826]
Modules linked in:
CPU: 1 PID: 5826 Comm: syz-executor330 Not tainted 5.15.148-syzkaller-00718-g993bed180178 #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024

RIP: 0010:rcu_preempt_read_exit kernel/rcu/tree_plugin.h:380 [inline]
RIP: 0010:__rcu_read_unlock+0x29/0xd0 kernel/rcu/tree_plugin.h:419
Code: 00 55 48 89 e5 41 57 41 56 41 55 41 54 53 49 bf 00 00 00 00 00 fc ff df 65 4c 8b 35 61 5b a5 7e 4d 8d a6 4c 04 00 00 4d 89 e5 <49> c1 ed 03 43 0f b6 44 3d 00 84 c0 75 49 41 8b 1c 24 ff cb 43 0f
RSP: 0018:ffffc90004e16868 EFLAGS: 00000293

RAX: ffffffff84aef09b RBX: 0000000000000004 RCX: ffff8881114e13c0
RDX: 0000000000000000 RSI: 0000000000000005 RDI: 00000000ffffffff
RBP: ffffc90004e16890 R08: ffffffff84aef091 R09: ffffed1021c80bd1
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff8881114e180c
R13: ffff8881114e180c R14: ffff8881114e13c0 R15: dffffc0000000000
FS: 00007f02e5f716c0(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000

CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 0000000020001c40 CR3: 00000001211ea000 CR4: 00000000003506a0

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
</IRQ>

<TASK>
rcu_read_unlock include/linux/rcupdate.h:728 [inline]
tipc_sk_lookup+0x542/0x650 net/tipc/socket.c:3002
tipc_sk_rcv+0x459/0x1b50 net/tipc/socket.c:2492
tipc_node_xmit+0x34e/0xe40 net/tipc/node.c:1703
tipc_node_xmit_skb+0x153/0x1b0 net/tipc/node.c:1768
tipc_sk_rcv+0x1690/0x1b50 net/tipc/socket.c:2522
tipc_node_xmit+0x34e/0xe40 net/tipc/node.c:1703
tipc_sk_push_backlog net/tipc/socket.c:1316 [inline]
tipc_sk_filter_connect net/tipc/socket.c:2255 [inline]
tipc_sk_filter_rcv+0x194e/0x3380 net/tipc/socket.c:2364
tipc_sk_enqueue net/tipc/socket.c:2445 [inline]
tipc_sk_rcv+0x80c/0x1b50 net/tipc/socket.c:2497
tipc_node_xmit+0x34e/0xe40 net/tipc/node.c:1703
tipc_node_xmit_skb net/tipc/node.c:1768 [inline]
tipc_node_distr_xmit+0x36a/0x4d0 net/tipc/node.c:1783
tipc_sk_backlog_rcv+0x18b/0x210 net/tipc/socket.c:2412
sk_backlog_rcv include/net/sock.h:1069 [inline]
__release_sock+0x145/0x410 net/core/sock.c:2719
release_sock+0x65/0x1b0 net/core/sock.c:3270
tipc_release+0xee9/0x1300 net/tipc/socket.c:652
__sock_release net/socket.c:649 [inline]
sock_close+0xdf/0x270 net/socket.c:1336
__fput+0x3fe/0x910 fs/file_table.c:280
____fput+0x15/0x20 fs/file_table.c:308
task_work_run+0x129/0x190 kernel/task_work.c:164
ptrace_notify+0x29e/0x350 kernel/signal.c:2388
ptrace_report_syscall include/linux/tracehook.h:66 [inline]
tracehook_report_syscall_exit include/linux/tracehook.h:130 [inline]
arch_syscall_exit_tracehook include/linux/entry-common.h:297 [inline]
syscall_exit_work kernel/entry/common.c:256 [inline]
syscall_exit_to_user_mode_prepare kernel/entry/common.c:283 [inline]
__syscall_exit_to_user_mode_work kernel/entry/common.c:288 [inline]
syscall_exit_to_user_mode+0xac/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:0x7f02e5fb0669
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f02e5f71218 EFLAGS: 00000246 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 00007f02e603a328 RCX: 00007f02e5fb0669
RDX: 00007f02e5fb0669 RSI: 00000000000f4240 RDI: 0000000000000004
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: ffffffffffffffb0
R13: 00007f02e603a320 R14: 00007f02e603a32c R15: 00007f02e6007064
</TASK>

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: eef3b6e52937 ANDROID: KVM: arm64: Fix TLB invalidation whe..
git tree: android14-6.1
console+strace: https://syzkaller.appspot.com/x/log.txt?x=166732c9180000
kernel config: https://syzkaller.appspot.com/x/.config?x=54c503ca94c7e582
dashboard link: https://syzkaller.appspot.com/bug?extid=590c02cc06f6cd2951e1

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=11f9dc6e180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=117a2c41180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2821fbb60763/disk-eef3b6e5.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bc0045a39cbd/vmlinux-eef3b6e5.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1b4198d13d12/bzImage-eef3b6e5.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:

Reported-by: syzbot+590c02...@syzkaller.appspotmail.com

RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: ffffffffffffffb0

R13: 00007f1842350320 R14: 00007f184235032c R15: 00007f184231d064
</TASK>
watchdog: BUG: soft lockup - CPU#1 stuck for 225s! [syz-executor403:1287]
Modules linked in:
CPU: 1 PID: 1287 Comm: syz-executor403 Not tainted 6.1.68-syzkaller-00096-geef3b6e52937 #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024

RIP: 0010:check_kcov_mode kernel/kcov.c:184 [inline]
RIP: 0010:__sanitizer_cov_trace_pc+0x36/0x60 kernel/kcov.c:207
Code: a0 fc 8c 7e 65 8b 15 a1 fc 8c 7e f7 c2 00 01 ff 00 74 11 f7 c2 00 01 00 00 74 35 83 b9 6c 0b 00 00 00 74 2c 8b 91 48 0b 00 00 <83> fa 02 75 21 48 8b 91 50 0b 00 00 48 8b 32 48 8d 7e 01 8b 89 4c
RSP: 0018:ffffc90001b16910 EFLAGS: 00000246
RAX: ffffffff84da64a1 RBX: 0000000000000000 RCX: ffff888112f85100
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90001b16910 R08: ffffffff84da52be R09: ffffed1024660d14
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff888123306800 R14: 000000009421ff59 R15: ffffc90001b16d20
FS: 00007f18422876c0(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000

CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 0000000020001c40 CR3: 0000000123621000 CR4: 00000000003506a0

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
</IRQ>
<TASK>

tipc_sk_rcv+0x1671/0x1c40 net/tipc/socket.c:2496

tipc_node_xmit+0x34e/0xe40 net/tipc/node.c:1703
tipc_node_xmit_skb+0x153/0x1b0 net/tipc/node.c:1768

tipc_sk_rcv+0x1787/0x1c40 net/tipc/socket.c:2522

tipc_node_xmit+0x34e/0xe40 net/tipc/node.c:1703
tipc_sk_push_backlog net/tipc/socket.c:1316 [inline]
tipc_sk_filter_connect net/tipc/socket.c:2255 [inline]

tipc_sk_filter_rcv+0x194e/0x3390 net/tipc/socket.c:2364
tipc_sk_enqueue net/tipc/socket.c:2445 [inline]
tipc_sk_rcv+0x815/0x1c40 net/tipc/socket.c:2497

tipc_node_xmit+0x34e/0xe40 net/tipc/node.c:1703
tipc_node_xmit_skb net/tipc/node.c:1768 [inline]
tipc_node_distr_xmit+0x36a/0x4d0 net/tipc/node.c:1783
tipc_sk_backlog_rcv+0x18b/0x210 net/tipc/socket.c:2412

sk_backlog_rcv include/net/sock.h:1129 [inline]
__release_sock+0x145/0x410 net/core/sock.c:2932
release_sock+0x65/0x1b0 net/core/sock.c:3506
tipc_release+0xf10/0x1310 net/tipc/socket.c:652
__sock_release net/socket.c:652 [inline]
sock_close+0xdf/0x270 net/socket.c:1387
__fput+0x3ab/0x870 fs/file_table.c:320
____fput+0x15/0x20 fs/file_table.c:348
task_work_run+0x24d/0x2e0 kernel/task_work.c:179
ptrace_notify+0x29e/0x350 kernel/signal.c:2375
ptrace_report_syscall include/linux/ptrace.h:420 [inline]
ptrace_report_syscall_exit include/linux/ptrace.h:482 [inline]
syscall_exit_work kernel/entry/common.c:252 [inline]
syscall_exit_to_user_mode_prepare kernel/entry/common.c:279 [inline]
__syscall_exit_to_user_mode_work kernel/entry/common.c:284 [inline]
syscall_exit_to_user_mode+0xa2/0x140 kernel/entry/common.c:297
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f18422c6669

Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48

RSP: 002b:00007f1842287218 EFLAGS: 00000246 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 00007f1842350328 RCX: 00007f18422c6669
RDX: 00007f18422c6669 RSI: 00000000000f4240 RDI: 0000000000000004

RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: ffffffffffffffb0

R13: 00007f1842350320 R14: 00007f184235032c R15: 00007f184231d064

[syzbot]

Bug presence analysis results: the bug reproduces only on Android 6.1.

syzbot has run the reproducer on other relevant kernel trees and got
the following results:

android14-6.1 (commit eef3b6e52937) on 2024/03/27:
BUG: soft lockup in sock_close
Report: https://syzkaller.appspot.com/x/report.txt?x=13ee0546180000

lts (commit 883d1a956208) on 2024/03/27:
Didn't crash.

upstream (commit 7033999ecd7b) on 2024/03/27:
Didn't crash.

More details can be found at:
https://syzkaller.appspot.com/bug?extid=590c02cc06f6cd2951e1

[syzbot]

syzbot suspects this issue was fixed by commit:

commit 11e8ecc5b86037fec43d07b1c162e233e131b1d9
Author: Jakub Sitnicki <ja...@cloudflare.com>
Date: Mon May 27 11:20:07 2024 +0000

bpf: Allow delete from sockmap/sockhash only if update is allowed

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17afb287980000
start commit: 70e1a731d986 Revert "regmap: Add bulk read/write callbacks..
git tree: android13-5.15-lts
kernel config: https://syzkaller.appspot.com/x/.config?x=8b7efdc8766bd1db
dashboard link: https://syzkaller.appspot.com/bug?extid=62469057aed52ef281ed
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1143c15d980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10974a6b980000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: bpf: Allow delete from sockmap/sockhash only if update is allowed

For information about bisection process see: https://goo.gl/tpsmEJ#bisection