ci starts bisection 2022-08-03 09:56:58.84927749 +0000 UTC m=+79917.786917993 bisecting fixing commit since 88084a3df1672e131ddc1b4e39eeacfd39864acf building syzkaller on 1434eec0b84075b7246560cfa89f20cdb3d8077f testing commit 88084a3df1672e131ddc1b4e39eeacfd39864acf compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: e8c2c3a142c37ee1b514e2161e8b0ba331dda18232b927164d685b464416ddbf all runs: crashed: WARNING: bad unlock balance in rxrpc_do_sendmsg testing current HEAD e2b542100719a93f8cdf6d90185410d38a57a4c1 testing commit e2b542100719a93f8cdf6d90185410d38a57a4c1 compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: 3fdd0f7d1e4196ff2aec4e22f3fd73e6908a632207be430e229cf639fc4a7375 run #0: basic kernel testing failed: BUG: program execution failed: executor NUM: failed to write control pipe: write |NUM: broken pipe run #1: crashed: WARNING: bad unlock balance in rxrpc_do_sendmsg run #2: crashed: WARNING: bad unlock balance in rxrpc_do_sendmsg run #3: crashed: WARNING: bad unlock balance in rxrpc_do_sendmsg run #4: crashed: WARNING: bad unlock balance in rxrpc_do_sendmsg run #5: crashed: WARNING: bad unlock balance in rxrpc_do_sendmsg run #6: crashed: WARNING: bad unlock balance in rxrpc_do_sendmsg run #7: crashed: WARNING: bad unlock balance in rxrpc_do_sendmsg run #8: crashed: WARNING: bad unlock balance in rxrpc_do_sendmsg run #9: crashed: WARNING: bad unlock balance in rxrpc_do_sendmsg revisions tested: 2, total time: 21m6.391576377s (build: 14m21.440130267s, test: 6m18.542423695s) the crash still happens on HEAD commit msg: Merge tag 'flexible-array-transformations-UAPI-6.0-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gustavoars/linux crash: WARNING: bad unlock balance in rxrpc_do_sendmsg ===================================== WARNING: bad unlock balance detected! 5.19.0-syzkaller #0 Not tainted ------------------------------------- syz-executor.0/4094 is trying to release lock (&call->user_mutex) at: [] rxrpc_do_sendmsg+0x851/0x1110 net/rxrpc/sendmsg.c:754 but there are no more locks to release! other info that might help us debug this: no locks held by syz-executor.0/4094. stack backtrace: CPU: 1 PID: 4094 Comm: syz-executor.0 Not tainted 5.19.0-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x57/0x7d lib/dump_stack.c:106 print_unlock_imbalance_bug include/trace/events/lock.h:69 [inline] __lock_release kernel/locking/lockdep.c:5333 [inline] lock_release.cold+0x49/0x4e kernel/locking/lockdep.c:5686 __mutex_unlock_slowpath+0x99/0x5e0 kernel/locking/mutex.c:907 rxrpc_do_sendmsg+0x851/0x1110 net/rxrpc/sendmsg.c:754 sock_sendmsg_nosec net/socket.c:714 [inline] sock_sendmsg+0xab/0xe0 net/socket.c:734 ____sys_sendmsg+0x5c2/0x7a0 net/socket.c:2485 ___sys_sendmsg+0xdb/0x160 net/socket.c:2539 __sys_sendmsg+0xc3/0x160 net/socket.c:2568 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f552b689109 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f552c77d168 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 00007f552b79bf60 RCX: 00007f552b689109 RDX: 0000000000000000 RSI: 0000000020000000 RDI: 0000000000000003 RBP: 00007f552b6e305d R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffce59973ef R14: 00007f552c77d300 R15: 0000000000022000