====================================================== WARNING: possible circular locking dependency detected 6.1.114-syzkaller #0 Not tainted ------------------------------------------------------ syz.5.278/6177 is trying to acquire lock: ffff888026679450 ((work_completion)(&new_smc->smc_listen_work)){+.+.}-{0:0}, at: __flush_work+0xe5/0xad0 kernel/workqueue.c:3072 but task is already holding lock: ffff888026678130 (sk_lock-AF_SMC/1){+.+.}-{0:0}, at: smc_release+0x22d/0x530 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_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5662 lock_sock_nested+0x44/0x100 net/core/sock.c:3485 smc_listen_out+0x113/0x3d0 net/smc/af_smc.c:1864 process_one_work+0x8a9/0x11d0 kernel/workqueue.c:2292 worker_thread+0xa47/0x1200 kernel/workqueue.c:2439 kthread+0x28d/0x320 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:3090 [inline] check_prevs_add kernel/locking/lockdep.c:3209 [inline] validate_chain+0x1661/0x5950 kernel/locking/lockdep.c:3825 __lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5049 lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5662 __flush_work+0xfe/0xad0 kernel/workqueue.c:3072 __cancel_work_timer+0x519/0x6a0 kernel/workqueue.c:3163 smc_clcsock_release+0x5e/0xe0 net/smc/smc_close.c:29 __smc_release+0x678/0x7f0 net/smc/af_smc.c:300 smc_close_non_accepted+0xd4/0x1e0 net/smc/af_smc.c:1798 smc_close_cleanup_listen net/smc/smc_close.c:45 [inline] smc_close_active+0xa75/0xe20 net/smc/smc_close.c:225 __smc_release+0xa0/0x7f0 net/smc/af_smc.c:276 smc_release+0x2d5/0x530 net/smc/af_smc.c:343 __sock_release net/socket.c:654 [inline] sock_close+0xcd/0x230 net/socket.c:1400 __fput+0x3f6/0x8d0 fs/file_table.c:320 task_work_run+0x246/0x300 kernel/task_work.c:203 resume_user_mode_work include/linux/resume_user_mode.h:49 [inline] exit_to_user_mode_loop+0xde/0x100 kernel/entry/common.c:177 exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:210 __syscall_exit_to_user_mode_work kernel/entry/common.c:292 [inline] syscall_exit_to_user_mode+0x60/0x270 kernel/entry/common.c:303 do_syscall_64+0x47/0xb0 arch/x86/entry/common.c:87 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.5.278/6177: #0: ffff88802778ee10 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline] #0: ffff88802778ee10 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: __sock_release net/socket.c:653 [inline] #0: ffff88802778ee10 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: sock_close+0x98/0x230 net/socket.c:1400 #1: ffff888026678130 (sk_lock-AF_SMC/1){+.+.}-{0:0}, at: smc_release+0x22d/0x530 stack backtrace: CPU: 0 PID: 6177 Comm: syz.5.278 Not tainted 6.1.114-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106 check_noncircular+0x2fa/0x3b0 kernel/locking/lockdep.c:2170 check_prev_add kernel/locking/lockdep.c:3090 [inline] check_prevs_add kernel/locking/lockdep.c:3209 [inline] validate_chain+0x1661/0x5950 kernel/locking/lockdep.c:3825 __lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5049 lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5662 __flush_work+0xfe/0xad0 kernel/workqueue.c:3072 __cancel_work_timer+0x519/0x6a0 kernel/workqueue.c:3163 smc_clcsock_release+0x5e/0xe0 net/smc/smc_close.c:29 __smc_release+0x678/0x7f0 net/smc/af_smc.c:300 smc_close_non_accepted+0xd4/0x1e0 net/smc/af_smc.c:1798 smc_close_cleanup_listen net/smc/smc_close.c:45 [inline] smc_close_active+0xa75/0xe20 net/smc/smc_close.c:225 __smc_release+0xa0/0x7f0 net/smc/af_smc.c:276 smc_release+0x2d5/0x530 net/smc/af_smc.c:343 __sock_release net/socket.c:654 [inline] sock_close+0xcd/0x230 net/socket.c:1400 __fput+0x3f6/0x8d0 fs/file_table.c:320 task_work_run+0x246/0x300 kernel/task_work.c:203 resume_user_mode_work include/linux/resume_user_mode.h:49 [inline] exit_to_user_mode_loop+0xde/0x100 kernel/entry/common.c:177 exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:210 __syscall_exit_to_user_mode_work kernel/entry/common.c:292 [inline] syscall_exit_to_user_mode+0x60/0x270 kernel/entry/common.c:303 do_syscall_64+0x47/0xb0 arch/x86/entry/common.c:87 entry_SYSCALL_64_after_hwframe+0x68/0xd2 RIP: 0033:0x7fc91377e719 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fc914513038 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4 RAX: 0000000000000000 RBX: 00007fc913935f80 RCX: 00007fc91377e719 RDX: 0000000000000000 RSI: ffffffffffffffff RDI: 0000000000000004 RBP: 00007fc9137f132e R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007fc913935f80 R15: 00007ffc05b8e858