ci starts bisection 2023-06-13 02:58:56.419358134 +0000 UTC m=+29252.650060761 bisecting fixing commit since c183e6c3ec342624c43269c099050d01eeb67e63 building syzkaller on ab32d50881df9f96f2af301aadca62ad00b7e099 ensuring issue is reproducible on original commit c183e6c3ec342624c43269c099050d01eeb67e63 testing commit c183e6c3ec342624c43269c099050d01eeb67e63 gcc compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: c915be763347d34a85c2e5317ff3a19b80393a9abd3ebadd0c1f5b1b15177684 run #0: crashed: possible deadlock in rds_wake_sk_sleep run #1: crashed: possible deadlock in rds_wake_sk_sleep run #2: crashed: possible deadlock in rds_wake_sk_sleep run #3: crashed: possible deadlock in rds_message_put run #4: crashed: possible deadlock in rds_wake_sk_sleep run #5: crashed: possible deadlock in rds_wake_sk_sleep run #6: crashed: possible deadlock in rds_message_put run #7: crashed: possible deadlock in rds_wake_sk_sleep run #8: crashed: possible deadlock in rds_wake_sk_sleep run #9: crashed: possible deadlock in rds_wake_sk_sleep run #10: crashed: possible deadlock in rds_wake_sk_sleep run #11: crashed: possible deadlock in rds_message_put run #12: crashed: possible deadlock in rds_wake_sk_sleep run #13: crashed: possible deadlock in rds_wake_sk_sleep run #14: crashed: possible deadlock in rds_wake_sk_sleep run #15: crashed: possible deadlock in rds_wake_sk_sleep run #16: crashed: possible deadlock in rds_wake_sk_sleep run #17: crashed: possible deadlock in rds_wake_sk_sleep run #18: crashed: possible deadlock in rds_wake_sk_sleep run #19: crashed: possible deadlock in rds_wake_sk_sleep testing current HEAD ccbe64be1533878f1dd3e7e28cfc33db60361bca testing commit ccbe64be1533878f1dd3e7e28cfc33db60361bca gcc compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: 19e45b4e562f98a0ab165edec8f5be460e2bc74d89a0970d27c646b0438c416a run #0: crashed: possible deadlock in rds_wake_sk_sleep run #1: crashed: possible deadlock in rds_wake_sk_sleep run #2: crashed: possible deadlock in rds_wake_sk_sleep run #3: crashed: possible deadlock in rds_wake_sk_sleep run #4: crashed: possible deadlock in rds_wake_sk_sleep run #5: crashed: possible deadlock in rds_message_put run #6: crashed: possible deadlock in rds_wake_sk_sleep run #7: crashed: possible deadlock in rds_wake_sk_sleep run #8: crashed: possible deadlock in rds_wake_sk_sleep run #9: crashed: possible deadlock in rds_wake_sk_sleep crash still not fixed/happens on the oldest tested release revisions tested: 2, total time: 29m40.210883825s (build: 18m9.10504558s, test: 10m23.781004417s) crash still not fixed on HEAD or HEAD had kernel test errors commit msg: Merge branch 'net-flower-add-cfm-support' crash: possible deadlock in rds_wake_sk_sleep ====================================================== WARNING: possible circular locking dependency detected 6.4.0-rc5-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.0/5607 is trying to acquire lock: ffff8880793d2530 (&rs->rs_recv_lock){....}-{2:2}, at: rds_wake_sk_sleep+0x1e/0xc0 net/rds/af_rds.c:109 but task is already holding lock: ffff88807d8a5900 (&rm->m_rs_lock){....}-{2:2}, at: rds_send_remove_from_sock+0x1e7/0x9a0 net/rds/send.c:628 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&rm->m_rs_lock){....}-{2:2}: __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline] _raw_spin_lock_irqsave+0x3d/0x60 kernel/locking/spinlock.c:162 rds_message_purge net/rds/message.c:138 [inline] rds_message_put+0x171/0xab0 net/rds/message.c:180 rds_clear_recv_queue+0x1c9/0x350 net/rds/recv.c:768 rds_release+0xce/0x360 net/rds/af_rds.c:73 __sock_release+0xbb/0x280 net/socket.c:653 sock_close+0x13/0x20 net/socket.c:1385 __fput+0x1fa/0x9a0 fs/file_table.c:321 task_work_run+0x12f/0x220 kernel/task_work.c:179 resume_user_mode_work include/linux/resume_user_mode.h:49 [inline] exit_to_user_mode_loop kernel/entry/common.c:171 [inline] exit_to_user_mode_prepare+0x210/0x240 kernel/entry/common.c:204 __syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline] syscall_exit_to_user_mode+0x1d/0x50 kernel/entry/common.c:297 do_syscall_64+0x46/0xb0 arch/x86/entry/common.c:86 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #0 (&rs->rs_recv_lock){....}-{2:2}: check_prev_add kernel/locking/lockdep.c:3113 [inline] check_prevs_add kernel/locking/lockdep.c:3232 [inline] validate_chain kernel/locking/lockdep.c:3847 [inline] __lock_acquire+0x2fcd/0x5f30 kernel/locking/lockdep.c:5088 lock_acquire kernel/locking/lockdep.c:5705 [inline] lock_acquire+0x1b1/0x520 kernel/locking/lockdep.c:5670 __raw_read_lock_irqsave include/linux/rwlock_api_smp.h:160 [inline] _raw_read_lock_irqsave+0x49/0x90 kernel/locking/spinlock.c:236 rds_wake_sk_sleep+0x1e/0xc0 net/rds/af_rds.c:109 rds_send_remove_from_sock+0x256/0x9a0 net/rds/send.c:634 rds_send_path_drop_acked+0x27a/0x360 net/rds/send.c:710 rds_tcp_write_space+0x19a/0x5c0 net/rds/tcp_send.c:198 tcp_new_space net/ipv4/tcp_input.c:5483 [inline] tcp_check_space+0xe2/0x730 net/ipv4/tcp_input.c:5502 tcp_data_snd_check net/ipv4/tcp_input.c:5511 [inline] tcp_rcv_established+0x763/0x2040 net/ipv4/tcp_input.c:6021 tcp_v4_do_rcv+0x532/0x800 net/ipv4/tcp_ipv4.c:1726 sk_backlog_rcv include/net/sock.h:1115 [inline] __release_sock+0x117/0x360 net/core/sock.c:2961 release_sock+0x4e/0x170 net/core/sock.c:3528 rds_send_xmit+0x882/0x2380 net/rds/send.c:422 rds_sendmsg+0x1da3/0x29e0 net/rds/send.c:1381 sock_sendmsg_nosec net/socket.c:724 [inline] sock_sendmsg+0xc0/0x150 net/socket.c:747 __sys_sendto+0x1c5/0x290 net/socket.c:2133 __do_sys_sendto net/socket.c:2145 [inline] __se_sys_sendto net/socket.c:2141 [inline] __x64_sys_sendto+0xdc/0x1b0 net/socket.c:2141 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&rm->m_rs_lock); lock(&rs->rs_recv_lock); lock(&rm->m_rs_lock); rlock(&rs->rs_recv_lock); *** DEADLOCK *** 3 locks held by syz-executor.0/5607: #0: ffff8880258ad6f0 (k-sk_lock-AF_INET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1710 [inline] #0: ffff8880258ad6f0 (k-sk_lock-AF_INET){+.+.}-{0:0}, at: tcp_sock_set_cork+0x12/0x70 net/ipv4/tcp.c:3238 #1: ffff8880258ad978 (k-clock-AF_INET){++.-}-{2:2}, at: rds_tcp_write_space+0x24/0x5c0 net/rds/tcp_send.c:184 #2: ffff88807d8a5900 (&rm->m_rs_lock){....}-{2:2}, at: rds_send_remove_from_sock+0x1e7/0x9a0 net/rds/send.c:628 stack backtrace: CPU: 0 PID: 5607 Comm: syz-executor.0 Not tainted 6.4.0-rc5-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x64/0xb0 lib/dump_stack.c:106 check_noncircular+0x25f/0x2e0 kernel/locking/lockdep.c:2188 check_prev_add kernel/locking/lockdep.c:3113 [inline] check_prevs_add kernel/locking/lockdep.c:3232 [inline] validate_chain kernel/locking/lockdep.c:3847 [inline] __lock_acquire+0x2fcd/0x5f30 kernel/locking/lockdep.c:5088 lock_acquire kernel/locking/lockdep.c:5705 [inline] lock_acquire+0x1b1/0x520 kernel/locking/lockdep.c:5670 __raw_read_lock_irqsave include/linux/rwlock_api_smp.h:160 [inline] _raw_read_lock_irqsave+0x49/0x90 kernel/locking/spinlock.c:236 rds_wake_sk_sleep+0x1e/0xc0 net/rds/af_rds.c:109 rds_send_remove_from_sock+0x256/0x9a0 net/rds/send.c:634 rds_send_path_drop_acked+0x27a/0x360 net/rds/send.c:710 rds_tcp_write_space+0x19a/0x5c0 net/rds/tcp_send.c:198 tcp_new_space net/ipv4/tcp_input.c:5483 [inline] tcp_check_space+0xe2/0x730 net/ipv4/tcp_input.c:5502 tcp_data_snd_check net/ipv4/tcp_input.c:5511 [inline] tcp_rcv_established+0x763/0x2040 net/ipv4/tcp_input.c:6021 tcp_v4_do_rcv+0x532/0x800 net/ipv4/tcp_ipv4.c:1726 sk_backlog_rcv include/net/sock.h:1115 [inline] __release_sock+0x117/0x360 net/core/sock.c:2961 release_sock+0x4e/0x170 net/core/sock.c:3528 rds_send_xmit+0x882/0x2380 net/rds/send.c:422 rds_sendmsg+0x1da3/0x29e0 net/rds/send.c:1381 sock_sendmsg_nosec net/socket.c:724 [inline] sock_sendmsg+0xc0/0x150 net/socket.c:747 __sys_sendto+0x1c5/0x290 net/socket.c:2133 __do_sys_sendto net/socket.c:2145 [inline] __se_sys_sendto net/socket.c:2141 [inline] __x64_sys_sendto+0xdc/0x1b0 net/socket.c:2141 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f5034e8c0a9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 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 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f5035ba2168 EFLAGS: 00000246 ORIG_RAX: 000000000000002c RAX: ffffffffffffffda RBX: 00007f5034fac050 RCX: 00007f5034e8c0a9 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000004 RBP: 00007f5034ee7ae9 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000040 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffd0ae70b6f R14: 00007f5035ba2300 R15: 0000000000022000