====================================================== WARNING: possible circular locking dependency detected 6.7.0-rc8-syzkaller-00126-gac631873c9e7 #0 Not tainted ------------------------------------------------------ syz-executor.0/5947 is trying to acquire lock: ffff8880791c6900 (&rm->m_rs_lock){....}-{2:2}, at: rds_message_purge net/rds/message.c:138 [inline] ffff8880791c6900 (&rm->m_rs_lock){....}-{2:2}, at: rds_message_put+0x1dd/0xc50 net/rds/message.c:180 but task is already holding lock: ffff88807cfafa70 (&rs->rs_recv_lock){....}-{2:2}, at: rds_clear_recv_queue+0x33/0x350 net/rds/recv.c:762 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&rs->rs_recv_lock){....}-{2:2}: __raw_read_lock_irqsave include/linux/rwlock_api_smp.h:160 [inline] _raw_read_lock_irqsave+0x46/0x90 kernel/locking/spinlock.c:236 rds_wake_sk_sleep+0x23/0xe0 net/rds/af_rds.c:109 rds_send_remove_from_sock+0x1e9/0xa50 net/rds/send.c:634 rds_send_path_drop_acked+0x2f4/0x3c0 net/rds/send.c:710 rds_tcp_write_space+0x1b5/0x6d0 net/rds/tcp_send.c:199 tcp_new_space net/ipv4/tcp_input.c:5633 [inline] tcp_check_space+0x178/0x8c0 net/ipv4/tcp_input.c:5652 tcp_data_snd_check net/ipv4/tcp_input.c:5661 [inline] tcp_rcv_established+0x953/0x20e0 net/ipv4/tcp_input.c:6179 tcp_v4_do_rcv+0x68c/0xa10 net/ipv4/tcp_ipv4.c:1906 sk_backlog_rcv include/net/sock.h:1121 [inline] __release_sock+0x132/0x3b0 net/core/sock.c:2976 release_sock+0x5a/0x1f0 net/core/sock.c:3542 rds_send_xmit+0x164f/0x2490 net/rds/send.c:422 rds_sendmsg+0x2af0/0x31e0 net/rds/send.c:1381 sock_sendmsg_nosec net/socket.c:730 [inline] __sock_sendmsg+0xd5/0x180 net/socket.c:745 ____sys_sendmsg+0x6ac/0x940 net/socket.c:2586 ___sys_sendmsg+0x135/0x1d0 net/socket.c:2640 __sys_sendmsg+0x117/0x1e0 net/socket.c:2669 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x40/0x110 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b -> #0 (&rm->m_rs_lock){....}-{2:2}: check_prev_add kernel/locking/lockdep.c:3134 [inline] check_prevs_add kernel/locking/lockdep.c:3253 [inline] validate_chain kernel/locking/lockdep.c:3869 [inline] __lock_acquire+0x2433/0x3b20 kernel/locking/lockdep.c:5137 lock_acquire kernel/locking/lockdep.c:5754 [inline] lock_acquire+0x1ae/0x520 kernel/locking/lockdep.c:5719 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline] _raw_spin_lock_irqsave+0x3a/0x50 kernel/locking/spinlock.c:162 rds_message_purge net/rds/message.c:138 [inline] rds_message_put+0x1dd/0xc50 net/rds/message.c:180 rds_inc_put+0x13c/0x1a0 net/rds/recv.c:83 rds_clear_recv_queue+0x14c/0x350 net/rds/recv.c:768 rds_release+0xdb/0x3c0 net/rds/af_rds.c:73 __sock_release+0xae/0x260 net/socket.c:659 sock_close+0x1c/0x20 net/socket.c:1421 __fput+0x270/0xb70 fs/file_table.c:394 __fput_sync+0x47/0x50 fs/file_table.c:475 __do_sys_close fs/open.c:1587 [inline] __se_sys_close fs/open.c:1572 [inline] __x64_sys_close+0x87/0xf0 fs/open.c:1572 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x40/0x110 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&rs->rs_recv_lock); lock(&rm->m_rs_lock); lock(&rs->rs_recv_lock); lock(&rm->m_rs_lock); *** DEADLOCK *** 2 locks held by syz-executor.0/5947: #0: ffff888062d0c410 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:802 [inline] #0: ffff888062d0c410 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: __sock_release+0x86/0x260 net/socket.c:658 #1: ffff88807cfafa70 (&rs->rs_recv_lock){....}-{2:2}, at: rds_clear_recv_queue+0x33/0x350 net/rds/recv.c:762 stack backtrace: CPU: 1 PID: 5947 Comm: syz-executor.0 Not tainted 6.7.0-rc8-syzkaller-00126-gac631873c9e7 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xd9/0x1b0 lib/dump_stack.c:106 check_noncircular+0x317/0x400 kernel/locking/lockdep.c:2187 check_prev_add kernel/locking/lockdep.c:3134 [inline] check_prevs_add kernel/locking/lockdep.c:3253 [inline] validate_chain kernel/locking/lockdep.c:3869 [inline] __lock_acquire+0x2433/0x3b20 kernel/locking/lockdep.c:5137 lock_acquire kernel/locking/lockdep.c:5754 [inline] lock_acquire+0x1ae/0x520 kernel/locking/lockdep.c:5719 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline] _raw_spin_lock_irqsave+0x3a/0x50 kernel/locking/spinlock.c:162 rds_message_purge net/rds/message.c:138 [inline] rds_message_put+0x1dd/0xc50 net/rds/message.c:180 rds_inc_put+0x13c/0x1a0 net/rds/recv.c:83 rds_clear_recv_queue+0x14c/0x350 net/rds/recv.c:768 rds_release+0xdb/0x3c0 net/rds/af_rds.c:73 __sock_release+0xae/0x260 net/socket.c:659 sock_close+0x1c/0x20 net/socket.c:1421 __fput+0x270/0xb70 fs/file_table.c:394 __fput_sync+0x47/0x50 fs/file_table.c:475 __do_sys_close fs/open.c:1587 [inline] __se_sys_close fs/open.c:1572 [inline] __x64_sys_close+0x87/0xf0 fs/open.c:1572 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x40/0x110 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b RIP: 0033:0x7fd9e707b95a 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 f3 7d 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 53 7e 02 00 8b 44 24 RSP: 002b:00007ffd0bcbff00 EFLAGS: 00000293 ORIG_RAX: 0000000000000003 RAX: ffffffffffffffda RBX: 0000000000000005 RCX: 00007fd9e707b95a RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000004 RBP: 00007fd9e719d980 R08: 0000001b2ef60000 R09: 0000000000000001 R10: 00007ffd0bdce080 R11: 0000000000000293 R12: 000000000002193f R13: ffffffffffffffff R14: 00007fd9e6c00000 R15: 00000000000215fe