====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.0.1255/9668 is trying to acquire lock: ffff888032f80a68 ((work_completion)(&new_smc->smc_listen_work)){+.+.}-{0:0}, at: rcu_lock_acquire include/linux/rcupdate.h:309 [inline] ffff888032f80a68 ((work_completion)(&new_smc->smc_listen_work)){+.+.}-{0:0}, at: rcu_read_lock include/linux/rcupdate.h:849 [inline] ffff888032f80a68 ((work_completion)(&new_smc->smc_listen_work)){+.+.}-{0:0}, at: start_flush_work kernel/workqueue.c:4515 [inline] ffff888032f80a68 ((work_completion)(&new_smc->smc_listen_work)){+.+.}-{0:0}, at: __flush_work+0x101/0xd30 kernel/workqueue.c:4573 but task is already holding lock: ffff8880481d6660 (sk_lock-AF_SMC/1){+.+.}-{0:0}, at: smc_release+0x24d/0x550 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+0x41/0x100 net/core/sock.c:3837 smc_listen_out+0xd4/0x3d0 net/smc/af_smc.c:1940 smc_listen_work+0x81d/0x1410 net/smc/af_smc.c:-1 process_one_work kernel/workqueue.c:3495 [inline] process_scheduled_works+0xc3d/0x1630 kernel/workqueue.c:3578 worker_thread+0xa47/0xfb0 kernel/workqueue.c:3659 kthread+0x38b/0x480 kernel/kthread.c:436 ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 -> #0 ((work_completion)(&new_smc->smc_listen_work)){+.+.}-{0:0}: check_prev_add kernel/locking/lockdep.c:3209 [inline] check_prevs_add kernel/locking/lockdep.c:3328 [inline] validate_chain kernel/locking/lockdep.c:3952 [inline] __lock_acquire+0x164c/0x2de0 kernel/locking/lockdep.c:5288 lock_acquire+0x115/0x350 kernel/locking/lockdep.c:5942 touch_work_lockdep_map kernel/workqueue.c:4287 [inline] start_flush_work kernel/workqueue.c:4541 [inline] __flush_work+0x7a6/0xd30 kernel/workqueue.c:4573 __cancel_work_sync kernel/workqueue.c:4729 [inline] cancel_work_sync+0xb8/0xf0 kernel/workqueue.c:4766 smc_clcsock_release+0x60/0xf0 net/smc/smc_close.c:29 __smc_release+0x64e/0x7c0 net/smc/af_smc.c:318 smc_close_non_accepted+0xd5/0x1f0 net/smc/af_smc.c:1870 smc_close_cleanup_listen net/smc/smc_close.c:45 [inline] smc_close_active+0xbd8/0x1000 net/smc/smc_close.c:226 __smc_release+0x9c/0x7c0 net/smc/af_smc.c:294 smc_release+0x2c5/0x550 net/smc/af_smc.c:361 __sock_release+0xa0/0x1f0 net/socket.c:735 sock_close+0x1c/0x30 net/socket.c:1529 __fput+0x413/0xa50 fs/file_table.c:513 fput_close_sync+0x11f/0x240 fs/file_table.c:618 filp_close_sync+0x6e/0xa0 fs/open.c:1573 __range_close fs/file.c:919 [inline] __do_sys_close_range fs/file.c:1003 [inline] __se_sys_close_range+0xa77/0xef0 fs/file.c:954 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline] do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84 entry_SYSCALL_64_after_hwframe+0x77/0x7f 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 *** locks held by syz.0.1255/9668: 3, last CPU#1: #0: ffff888044010dc0 (&sb->s_type->i_mutex_key#13){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:1024 [inline] #0: ffff888044010dc0 (&sb->s_type->i_mutex_key#13){+.+.}-{4:4}, at: __sock_release+0x7a/0x1f0 net/socket.c:734 #1: ffff8880481d6660 (sk_lock-AF_SMC/1){+.+.}-{0:0}, at: smc_release+0x24d/0x550 net/smc/af_smc.c:-1 #2: ffffffff8ed5a3e0 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:309 [inline] #2: ffffffff8ed5a3e0 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:849 [inline] #2: ffffffff8ed5a3e0 (rcu_read_lock){....}-{1:3}, at: start_flush_work kernel/workqueue.c:4515 [inline] #2: ffffffff8ed5a3e0 (rcu_read_lock){....}-{1:3}, at: __flush_work+0x101/0xd30 kernel/workqueue.c:4573 stack backtrace: CPU: 1 UID: 0 PID: 9668 Comm: syz.0.1255 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026 Call Trace: dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120 print_circular_bug+0x2e2/0x300 kernel/locking/lockdep.c:2087 check_noncircular+0x12f/0x150 kernel/locking/lockdep.c:2219 check_prev_add kernel/locking/lockdep.c:3209 [inline] check_prevs_add kernel/locking/lockdep.c:3328 [inline] validate_chain kernel/locking/lockdep.c:3952 [inline] __lock_acquire+0x164c/0x2de0 kernel/locking/lockdep.c:5288 lock_acquire+0x115/0x350 kernel/locking/lockdep.c:5942 touch_work_lockdep_map kernel/workqueue.c:4287 [inline] start_flush_work kernel/workqueue.c:4541 [inline] __flush_work+0x7a6/0xd30 kernel/workqueue.c:4573 __cancel_work_sync kernel/workqueue.c:4729 [inline] cancel_work_sync+0xb8/0xf0 kernel/workqueue.c:4766 smc_clcsock_release+0x60/0xf0 net/smc/smc_close.c:29 __smc_release+0x64e/0x7c0 net/smc/af_smc.c:318 smc_close_non_accepted+0xd5/0x1f0 net/smc/af_smc.c:1870 smc_close_cleanup_listen net/smc/smc_close.c:45 [inline] smc_close_active+0xbd8/0x1000 net/smc/smc_close.c:226 __smc_release+0x9c/0x7c0 net/smc/af_smc.c:294 smc_release+0x2c5/0x550 net/smc/af_smc.c:361 __sock_release+0xa0/0x1f0 net/socket.c:735 sock_close+0x1c/0x30 net/socket.c:1529 __fput+0x413/0xa50 fs/file_table.c:513 fput_close_sync+0x11f/0x240 fs/file_table.c:618 filp_close_sync+0x6e/0xa0 fs/open.c:1573 __range_close fs/file.c:919 [inline] __do_sys_close_range fs/file.c:1003 [inline] __se_sys_close_range+0xa77/0xef0 fs/file.c:954 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline] do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f7f6c39e159 Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 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 e8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffdd868d7a8 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4 RAX: ffffffffffffffda RBX: 00007f7f6c627da0 RCX: 00007f7f6c39e159 RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003 RBP: 00007f7f6c627da0 R08: 00007f7f6c626038 R09: 0000000000000000 R10: 00000000005f75e4 R11: 0000000000000246 R12: 0000000000056034 R13: 00007f7f6c625fac R14: 0000000000055d8b R15: 00007ffdd868d8b0