====================================================== WARNING: possible circular locking dependency detected 6.13.0-rc3-syzkaller-00136-g8faabc041a00 #0 Not tainted ------------------------------------------------------ kworker/0:3/5833 is trying to acquire lock: ffff88807123e6a8 (&smc->clcsock_release_lock){+.+.}-{4:4}, at: smc_switch_to_fallback+0x2d/0xa00 net/smc/af_smc.c:903 but task is already holding lock: ffff88807123de58 (sk_lock-AF_INET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1617 [inline] ffff88807123de58 (sk_lock-AF_INET){+.+.}-{0:0}, at: smc_connect_work+0x53c/0xae0 net/smc/af_smc.c:1597 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (sk_lock-AF_INET){+.+.}-{0:0}: lock_sock_nested+0x3a/0xf0 net/core/sock.c:3622 lock_sock include/net/sock.h:1617 [inline] sockopt_lock_sock net/core/sock.c:1126 [inline] sockopt_lock_sock+0x54/0x70 net/core/sock.c:1117 do_ip_getsockopt+0x115c/0x2bf0 net/ipv4/ip_sockglue.c:1703 ip_getsockopt+0x9c/0x1e0 net/ipv4/ip_sockglue.c:1765 raw_getsockopt+0x4d/0x1e0 net/ipv4/raw.c:865 do_sock_getsockopt+0x3fe/0x870 net/socket.c:2374 __sys_getsockopt+0x12f/0x260 net/socket.c:2403 __do_sys_getsockopt net/socket.c:2410 [inline] __se_sys_getsockopt net/socket.c:2407 [inline] __x64_sys_getsockopt+0xbd/0x160 net/socket.c:2407 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #1 (rtnl_mutex){+.+.}-{4:4}: __mutex_lock_common kernel/locking/mutex.c:585 [inline] __mutex_lock+0x19b/0xa60 kernel/locking/mutex.c:735 do_ip_setsockopt+0xf9/0x38c0 net/ipv4/ip_sockglue.c:1077 ip_setsockopt+0x59/0xf0 net/ipv4/ip_sockglue.c:1417 ipv6_setsockopt+0x155/0x170 net/ipv6/ipv6_sockglue.c:988 tcp_setsockopt+0xa4/0x100 net/ipv4/tcp.c:4030 smc_setsockopt+0x1b4/0xc00 net/smc/af_smc.c:3078 do_sock_setsockopt+0x222/0x480 net/socket.c:2313 __sys_setsockopt+0x1a0/0x230 net/socket.c:2338 __do_sys_setsockopt net/socket.c:2344 [inline] __se_sys_setsockopt net/socket.c:2341 [inline] __x64_sys_setsockopt+0xbd/0x160 net/socket.c:2341 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 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:3161 [inline] check_prevs_add kernel/locking/lockdep.c:3280 [inline] validate_chain kernel/locking/lockdep.c:3904 [inline] __lock_acquire+0x249e/0x3c40 kernel/locking/lockdep.c:5226 lock_acquire.part.0+0x11b/0x380 kernel/locking/lockdep.c:5849 __mutex_lock_common kernel/locking/mutex.c:585 [inline] __mutex_lock+0x19b/0xa60 kernel/locking/mutex.c:735 smc_switch_to_fallback+0x2d/0xa00 net/smc/af_smc.c:903 smc_connect_fallback+0x42/0x240 net/smc/af_smc.c:937 __smc_connect+0xb6f/0x4890 net/smc/af_smc.c:1499 smc_connect_work+0x54f/0xae0 net/smc/af_smc.c:1610 process_one_work+0x958/0x1b30 kernel/workqueue.c:3229 process_scheduled_works kernel/workqueue.c:3310 [inline] worker_thread+0x6c8/0xf00 kernel/workqueue.c:3391 kthread+0x2c1/0x3a0 kernel/kthread.c:389 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 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 *** 3 locks held by kworker/0:3/5833: #0: ffff888030fcd548 ((wq_completion)smc_hs_wq){+.+.}-{0:0}, at: process_one_work+0x12cd/0x1b30 kernel/workqueue.c:3204 #1: ffffc90003ab7d80 ((work_completion)(&smc->connect_work)){+.+.}-{0:0}, at: process_one_work+0x8bb/0x1b30 kernel/workqueue.c:3205 #2: ffff88807123de58 (sk_lock-AF_INET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1617 [inline] #2: ffff88807123de58 (sk_lock-AF_INET){+.+.}-{0:0}, at: smc_connect_work+0x53c/0xae0 net/smc/af_smc.c:1597 stack backtrace: CPU: 0 UID: 0 PID: 5833 Comm: kworker/0:3 Not tainted 6.13.0-rc3-syzkaller-00136-g8faabc041a00 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/25/2024 Workqueue: smc_hs_wq smc_connect_work Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120 print_circular_bug+0x41c/0x610 kernel/locking/lockdep.c:2074 check_noncircular+0x31a/0x400 kernel/locking/lockdep.c:2206 check_prev_add kernel/locking/lockdep.c:3161 [inline] check_prevs_add kernel/locking/lockdep.c:3280 [inline] validate_chain kernel/locking/lockdep.c:3904 [inline] __lock_acquire+0x249e/0x3c40 kernel/locking/lockdep.c:5226 lock_acquire.part.0+0x11b/0x380 kernel/locking/lockdep.c:5849 __mutex_lock_common kernel/locking/mutex.c:585 [inline] __mutex_lock+0x19b/0xa60 kernel/locking/mutex.c:735 smc_switch_to_fallback+0x2d/0xa00 net/smc/af_smc.c:903 smc_connect_fallback+0x42/0x240 net/smc/af_smc.c:937 __smc_connect+0xb6f/0x4890 net/smc/af_smc.c:1499 smc_connect_work+0x54f/0xae0 net/smc/af_smc.c:1610 process_one_work+0x958/0x1b30 kernel/workqueue.c:3229 process_scheduled_works kernel/workqueue.c:3310 [inline] worker_thread+0x6c8/0xf00 kernel/workqueue.c:3391 kthread+0x2c1/0x3a0 kernel/kthread.c:389 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244