====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.6.2559/16329 is trying to acquire lock: ffff888054c14158 ((work_completion)(&new_smc->smc_listen_work)){+.+.}-{0:0}, at: __flush_work+0x109/0xac0 kernel/workqueue.c:3072 but task is already holding lock: ffff888054c12e30 (sk_lock-AF_SMC/1){+.+.}-{0:0}, at: smc_release+0x249/0x520 net/smc/af_smc.c:-1 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (sk_lock-AF_SMC/1){+.+.}-{0:0}: lock_sock_nested+0x44/0x100 net/core/sock.c:3505 smc_listen_out+0x105/0x3b0 net/smc/af_smc.c:1878 smc_listen_out_connected net/smc/af_smc.c:1898 [inline] smc_listen_decline net/smc/af_smc.c:1933 [inline] smc_listen_work+0x57c/0xd60 net/smc/af_smc.c:2476 process_one_work+0x8ab/0x1160 kernel/workqueue.c:2292 worker_thread+0xaf5/0x12a0 kernel/workqueue.c:2439 kthread+0x29d/0x330 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295 -> #0 ((work_completion)(&new_smc->smc_listen_work)){+.+.}-{0:0}: check_prev_add kernel/locking/lockdep.c:3095 [inline] check_prevs_add kernel/locking/lockdep.c:3214 [inline] validate_chain kernel/locking/lockdep.c:3830 [inline] __lock_acquire+0x2d18/0x7c40 kernel/locking/lockdep.c:5063 lock_acquire+0x1bb/0x4a0 kernel/locking/lockdep.c:5676 __flush_work+0x122/0xac0 kernel/workqueue.c:3072 __cancel_work_timer+0x3f4/0x560 kernel/workqueue.c:3163 smc_clcsock_release+0x5c/0xe0 net/smc/smc_close.c:29 __smc_release+0x644/0x7b0 net/smc/af_smc.c:312 smc_close_non_accepted+0xd1/0x1f0 net/smc/af_smc.c:1811 smc_close_cleanup_listen net/smc/smc_close.c:45 [inline] smc_close_active+0xae2/0xea0 net/smc/smc_close.c:225 __smc_release+0x9c/0x7b0 net/smc/af_smc.c:288 smc_release+0x2c1/0x520 net/smc/af_smc.c:355 __sock_release net/socket.c:654 [inline] sock_close+0xbf/0x210 net/socket.c:1400 __fput+0x20a/0x8b0 fs/file_table.c:320 task_work_run+0x1d0/0x260 kernel/task_work.c:203 exit_task_work include/linux/task_work.h:39 [inline] do_exit+0x9d5/0x2570 kernel/exit.c:881 do_group_exit+0x229/0x2e0 kernel/exit.c:1024 get_signal+0x1259/0x1340 kernel/signal.c:2872 arch_do_signal_or_restart+0xc4/0x1310 arch/x86/kernel/signal.c:871 exit_to_user_mode_loop+0x70/0x110 kernel/entry/common.c:174 exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:210 __syscall_exit_to_user_mode_work kernel/entry/common.c:292 [inline] syscall_exit_to_user_mode+0x16/0x40 kernel/entry/common.c:303 do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:82 entry_SYSCALL_64_after_hwframe+0x68/0xd2 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(sk_lock-AF_SMC/1); lock((work_completion)(&new_smc->smc_listen_work)); lock(sk_lock-AF_SMC/1); lock((work_completion)(&new_smc->smc_listen_work)); *** DEADLOCK *** 2 locks held by syz.6.2559/16329: #0: ffff888074bf6210 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline] #0: ffff888074bf6210 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: __sock_release net/socket.c:653 [inline] #0: ffff888074bf6210 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: sock_close+0x82/0x210 net/socket.c:1400 #1: ffff888054c12e30 (sk_lock-AF_SMC/1){+.+.}-{0:0}, at: smc_release+0x249/0x520 net/smc/af_smc.c:-1 stack backtrace: CPU: 1 PID: 16329 Comm: syz.6.2559 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/16/2026 Call Trace: dump_stack_lvl+0x188/0x24e lib/dump_stack.c:106 check_noncircular+0x296/0x330 kernel/locking/lockdep.c:2170 check_prev_add kernel/locking/lockdep.c:3095 [inline] check_prevs_add kernel/locking/lockdep.c:3214 [inline] validate_chain kernel/locking/lockdep.c:3830 [inline] __lock_acquire+0x2d18/0x7c40 kernel/locking/lockdep.c:5063 lock_acquire+0x1bb/0x4a0 kernel/locking/lockdep.c:5676 __flush_work+0x122/0xac0 kernel/workqueue.c:3072 __cancel_work_timer+0x3f4/0x560 kernel/workqueue.c:3163 smc_clcsock_release+0x5c/0xe0 net/smc/smc_close.c:29 __smc_release+0x644/0x7b0 net/smc/af_smc.c:312 smc_close_non_accepted+0xd1/0x1f0 net/smc/af_smc.c:1811 smc_close_cleanup_listen net/smc/smc_close.c:45 [inline] smc_close_active+0xae2/0xea0 net/smc/smc_close.c:225 __smc_release+0x9c/0x7b0 net/smc/af_smc.c:288 smc_release+0x2c1/0x520 net/smc/af_smc.c:355 __sock_release net/socket.c:654 [inline] sock_close+0xbf/0x210 net/socket.c:1400 __fput+0x20a/0x8b0 fs/file_table.c:320 task_work_run+0x1d0/0x260 kernel/task_work.c:203 exit_task_work include/linux/task_work.h:39 [inline] do_exit+0x9d5/0x2570 kernel/exit.c:881 do_group_exit+0x229/0x2e0 kernel/exit.c:1024 get_signal+0x1259/0x1340 kernel/signal.c:2872 arch_do_signal_or_restart+0xc4/0x1310 arch/x86/kernel/signal.c:871 exit_to_user_mode_loop+0x70/0x110 kernel/entry/common.c:174 exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:210 __syscall_exit_to_user_mode_work kernel/entry/common.c:292 [inline] syscall_exit_to_user_mode+0x16/0x40 kernel/entry/common.c:303 do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:82 entry_SYSCALL_64_after_hwframe+0x68/0xd2 RIP: 0033:0x7fbf9e39df99 Code: Unable to access opcode bytes at 0x7fbf9e39df6f. RSP: 002b:00007fbf9f194028 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: 0000000000000000 RBX: 00007fbf9e626180 RCX: 00007fbf9e39df99 RDX: 0000200000000200 RSI: 00000000400454ca RDI: 0000000000000009 RBP: 00007fbf9e434ec4 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fbf9e626218 R14: 00007fbf9e626180 R15: 00007ffe9d466df8