| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <000000000000bb900e061440909c@google.com> Date: Fri, 22 Mar 2024 07:23:18 -0700 From: syzbot <syzbot+10a41dc44eef71aa9450@...kaller.appspotmail.com> To: davem@...emloft.net, edumazet@...gle.com, jmaloy@...hat.com, kuba@...nel.org, linux-kernel@...r.kernel.org, netdev@...r.kernel.org, pabeni@...hat.com, syzkaller-bugs@...glegroups.com, tipc-discussion@...ts.sourceforge.net, ying.xue@...driver.com Subject: [syzbot] [tipc?] BUG: soft lockup in do_sock_setsockopt Hello, syzbot found the following issue on: HEAD commit: 707081b61156 Merge branch 'for-next/core', remote-tracking.. git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci console output: https://syzkaller.appspot.com/x/log.txt?x=16d23231180000 kernel config: https://syzkaller.appspot.com/x/.config?x=caeac3f3565b057a dashboard link: https://syzkaller.appspot.com/bug?extid=10a41dc44eef71aa9450 compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 userspace arch: arm64 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=126fea6e180000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=114e4c81180000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/6cad68bf7532/disk-707081b6.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/1a27e5400778/vmlinux-707081b6.xz kernel image: https://storage.googleapis.com/syzbot-assets/67dfc53755d0/Image-707081b6.gz.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+10a41dc44eef71aa9450@...kaller.appspotmail.com watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [syz-executor178:13146] Modules linked in: irq event stamp: 29265101 hardirqs last enabled at (29265100): [<ffff8000801dae10>] __local_bh_enable_ip+0x224/0x44c kernel/softirq.c:386 hardirqs last disabled at (29265101): [<ffff80008ad66a78>] __el1_irq arch/arm64/kernel/entry-common.c:533 [inline] hardirqs last disabled at (29265101): [<ffff80008ad66a78>] el1_interrupt+0x24/0x68 arch/arm64/kernel/entry-common.c:551 softirqs last enabled at (638): [<ffff80008a7fe730>] spin_unlock_bh include/linux/spinlock.h:396 [inline] softirqs last enabled at (638): [<ffff80008a7fe730>] tipc_skb_peek_port net/tipc/msg.h:1235 [inline] softirqs last enabled at (638): [<ffff80008a7fe730>] tipc_sk_rcv+0x34c/0x1888 net/tipc/socket.c:2494 softirqs last disabled at (640): [<ffff80008a7fe750>] spin_trylock_bh include/linux/spinlock.h:411 [inline] softirqs last disabled at (640): [<ffff80008a7fe750>] tipc_sk_rcv+0x36c/0x1888 net/tipc/socket.c:2499 CPU: 0 PID: 13146 Comm: syz-executor178 Not tainted 6.8.0-rc7-syzkaller-g707081b61156 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024 pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : lock_acquire+0x278/0x71c lr : lockdep_recursion_finish kernel/locking/lockdep.c:467 [inline] lr : lock_acquire+0x248/0x71c kernel/locking/lockdep.c:5756 sp : ffff80009ab86080 x29: ffff80009ab86190 x28: dfff800000000000 x27: ffff700013570c1c x26: ffff0001b3fffdc0 x25: ffff80008ee74ac0 x24: 0000000000000000 x23: 0000000000000000 x22: 0000000000000000 x21: 0000000000000000 x20: ffff80008ebebdc0 x19: ffff0001b3fffdc0 x18: ffff80009ab862e0 x17: 000000000000c55c x16: ffff80008ad6b1c0 x15: 0000000000000001 x14: ffff80008eca0458 x13: dfff800000000000 x12: 00000000af1c601b x11: 00000000a4e03a31 x10: 0000000000000003 x9 : 0000000000000000 x8 : 00000000000000c0 x7 : ffff80008a80b3f8 x6 : 0000000000000000 x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000002 x2 : 0000000000000008 x1 : ffff80008aedfba0 x0 : 0000000000000000 Call trace: __daif_local_irq_restore arch/arm64/include/asm/irqflags.h:176 [inline] arch_local_irq_restore arch/arm64/include/asm/irqflags.h:196 [inline] lock_acquire+0x278/0x71c kernel/locking/lockdep.c:5757 rcu_lock_acquire+0x40/0x4c include/linux/rcupdate.h:298 rcu_read_lock include/linux/rcupdate.h:750 [inline] tipc_sk_lookup+0xc8/0x8b4 net/tipc/socket.c:3003 tipc_sk_rcv+0x358/0x1888 net/tipc/socket.c:2495 tipc_node_xmit+0x1b0/0xdb0 net/tipc/node.c:1703 tipc_node_xmit_skb net/tipc/node.c:1768 [inline] tipc_node_distr_xmit+0x28c/0x3a4 net/tipc/node.c:1783 tipc_sk_rcv+0x1280/0x1888 net/tipc/socket.c:2504 tipc_node_xmit+0x1b0/0xdb0 net/tipc/node.c:1703 tipc_sk_push_backlog net/tipc/socket.c:1317 [inline] tipc_sk_filter_connect net/tipc/socket.c:2258 [inline] tipc_sk_filter_rcv+0x13f8/0x2cac net/tipc/socket.c:2367 tipc_sk_enqueue net/tipc/socket.c:2448 [inline] tipc_sk_rcv+0x6d0/0x1888 net/tipc/socket.c:2500 tipc_node_xmit+0x1b0/0xdb0 net/tipc/node.c:1703 tipc_node_xmit_skb net/tipc/node.c:1768 [inline] tipc_node_distr_xmit+0x28c/0x3a4 net/tipc/node.c:1783 tipc_sk_backlog_rcv+0x164/0x214 net/tipc/socket.c:2415 sk_backlog_rcv include/net/sock.h:1092 [inline] __release_sock+0x1a8/0x408 net/core/sock.c:2972 release_sock+0x68/0x1b8 net/core/sock.c:3538 sk_setsockopt+0xbdc/0x306c sock_setsockopt+0x68/0x80 net/core/sock.c:1548 do_sock_setsockopt+0x238/0x4e0 net/socket.c:2307 __sys_setsockopt+0x128/0x1a8 net/socket.c:2334 __do_sys_setsockopt net/socket.c:2343 [inline] __se_sys_setsockopt net/socket.c:2340 [inline] __arm64_sys_setsockopt+0xb8/0xd4 net/socket.c:2340 __invoke_syscall arch/arm64/kernel/syscall.c:34 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:48 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:133 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:152 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:712 el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:730 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598 --- 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 syzkaller@...glegroups.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
Powered by blists - more mailing lists