====================================================== WARNING: possible circular locking dependency detected 6.14.0-rc1-syzkaller-00197-gacdefab0dcbc #0 Not tainted ------------------------------------------------------ syz-executor304/5831 is trying to acquire lock: ffff888035068aa8 (&smc->clcsock_release_lock){+.+.}-{4:4}, at: smc_switch_to_fallback+0x35/0xd90 net/smc/af_smc.c:903 but task is already holding lock: ffff888035068258 (sk_lock-AF_INET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1624 [inline] ffff888035068258 (sk_lock-AF_INET){+.+.}-{0:0}, at: smc_sendmsg+0x55/0x530 net/smc/af_smc.c:2775 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (sk_lock-AF_INET){+.+.}-{0:0}: lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5851 lock_sock_nested+0x48/0x100 net/core/sock.c:3645 do_ip_setsockopt+0x1a2d/0x3cd0 net/ipv4/ip_sockglue.c:1078 ip_setsockopt+0x63/0x100 net/ipv4/ip_sockglue.c:1417 do_sock_setsockopt+0x3af/0x720 net/socket.c:2298 __sys_setsockopt net/socket.c:2323 [inline] __do_sys_setsockopt net/socket.c:2329 [inline] __se_sys_setsockopt net/socket.c:2326 [inline] __x64_sys_setsockopt+0x1ee/0x280 net/socket.c:2326 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #1 (rtnl_mutex){+.+.}-{4:4}: lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5851 __mutex_lock_common kernel/locking/mutex.c:585 [inline] __mutex_lock+0x19c/0x1010 kernel/locking/mutex.c:730 do_ip_setsockopt+0x127d/0x3cd0 net/ipv4/ip_sockglue.c:1077 ip_setsockopt+0x63/0x100 net/ipv4/ip_sockglue.c:1417 smc_setsockopt+0x275/0xe50 net/smc/af_smc.c:3081 do_sock_setsockopt+0x3af/0x720 net/socket.c:2298 __sys_setsockopt net/socket.c:2323 [inline] __do_sys_setsockopt net/socket.c:2329 [inline] __se_sys_setsockopt net/socket.c:2326 [inline] __x64_sys_setsockopt+0x1ee/0x280 net/socket.c:2326 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (&smc->clcsock_release_lock){+.+.}-{4:4}: check_prev_add kernel/locking/lockdep.c:3163 [inline] check_prevs_add kernel/locking/lockdep.c:3282 [inline] validate_chain+0x18ef/0x5920 kernel/locking/lockdep.c:3906 __lock_acquire+0x1397/0x2100 kernel/locking/lockdep.c:5228 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5851 __mutex_lock_common kernel/locking/mutex.c:585 [inline] __mutex_lock+0x19c/0x1010 kernel/locking/mutex.c:730 smc_switch_to_fallback+0x35/0xd90 net/smc/af_smc.c:903 smc_sendmsg+0x11f/0x530 net/smc/af_smc.c:2781 sock_sendmsg_nosec net/socket.c:713 [inline] __sock_sendmsg+0x221/0x270 net/socket.c:728 ____sys_sendmsg+0x52a/0x7e0 net/socket.c:2568 ___sys_sendmsg net/socket.c:2622 [inline] __sys_sendmsg+0x269/0x350 net/socket.c:2654 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f other info that might help us debug this: Chain exists of: &smc->clcsock_release_lock --> rtnl_mutex --> sk_lock-AF_INET Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(sk_lock-AF_INET); lock(rtnl_mutex); lock(sk_lock-AF_INET); lock(&smc->clcsock_release_lock); *** DEADLOCK *** 1 lock held by syz-executor304/5831: #0: ffff888035068258 (sk_lock-AF_INET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1624 [inline] #0: ffff888035068258 (sk_lock-AF_INET){+.+.}-{0:0}, at: smc_sendmsg+0x55/0x530 net/smc/af_smc.c:2775 stack backtrace: CPU: 1 UID: 0 PID: 5831 Comm: syz-executor304 Not tainted 6.14.0-rc1-syzkaller-00197-gacdefab0dcbc #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120 print_circular_bug+0x13a/0x1b0 kernel/locking/lockdep.c:2076 check_noncircular+0x36a/0x4a0 kernel/locking/lockdep.c:2208 check_prev_add kernel/locking/lockdep.c:3163 [inline] check_prevs_add kernel/locking/lockdep.c:3282 [inline] validate_chain+0x18ef/0x5920 kernel/locking/lockdep.c:3906 __lock_acquire+0x1397/0x2100 kernel/locking/lockdep.c:5228 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5851 __mutex_lock_common kernel/locking/mutex.c:585 [inline] __mutex_lock+0x19c/0x1010 kernel/locking/mutex.c:730 smc_switch_to_fallback+0x35/0xd90 net/smc/af_smc.c:903 smc_sendmsg+0x11f/0x530 net/smc/af_smc.c:2781 sock_sendmsg_nosec net/socket.c:713 [inline] __sock_sendmsg+0x221/0x270 net/socket.c:728 ____sys_sendmsg+0x52a/0x7e0 net/socket.c:2568 ___sys_sendmsg net/socket.c:2622 [inline] __sys_sendmsg+0x269/0x350 net/socket.c:2654 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f1dae01a369 Code: 48 83 c4 28 c3 e8 37 17 00 00 0f 1f 80 00 00 00 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:00007ffd2c2dabd8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 00007ffd2c2dada8 RCX: 00007f1dae01a369 RDX: 0000000020001090 RSI: 00004000000003c0 RDI: 0000000000000004 RBP: 00007f1dae08d610 R08: 00007ffd2c2dada8 R09: 00007ffd2c2dada8