====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Tainted: G U L ------------------------------------------------------ syz.2.7935/17968 is trying to acquire lock: ffff888046afe1d8 ((work_completion)(&new_smc->smc_listen_work)){+.+.}-{0:0}, at: touch_work_lockdep_map kernel/workqueue.c:3955 [inline] ffff888046afe1d8 ((work_completion)(&new_smc->smc_listen_work)){+.+.}-{0:0}, at: start_flush_work kernel/workqueue.c:4209 [inline] ffff888046afe1d8 ((work_completion)(&new_smc->smc_listen_work)){+.+.}-{0:0}, at: __flush_work+0x4d0/0xcc0 kernel/workqueue.c:4241 but task is already holding lock: ffff888046afe660 (sk_lock-AF_SMC/1){+.+.}-{0:0}, at: smc_release+0x3a5/0x620 net/smc/af_smc.c:339 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/0xf0 net/core/sock.c:3780 smc_listen_out+0x202/0x4a0 net/smc/af_smc.c:1924 smc_listen_out_connected net/smc/af_smc.c:1944 [inline] smc_listen_work+0x5a3/0x50b0 net/smc/af_smc.c:2466 process_one_work+0x9ba/0x1b20 kernel/workqueue.c:3257 process_scheduled_works kernel/workqueue.c:3340 [inline] worker_thread+0x6c8/0xf10 kernel/workqueue.c:3421 kthread+0x3c5/0x780 kernel/kthread.c:463 ret_from_fork+0x983/0xb10 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246 -> #0 ((work_completion)(&new_smc->smc_listen_work)){+.+.}-{0:0}: check_prev_add kernel/locking/lockdep.c:3165 [inline] check_prevs_add kernel/locking/lockdep.c:3284 [inline] validate_chain kernel/locking/lockdep.c:3908 [inline] __lock_acquire+0x1669/0x2890 kernel/locking/lockdep.c:5237 lock_acquire kernel/locking/lockdep.c:5868 [inline] lock_acquire+0x179/0x330 kernel/locking/lockdep.c:5825 touch_work_lockdep_map kernel/workqueue.c:3955 [inline] start_flush_work kernel/workqueue.c:4209 [inline] __flush_work+0x4e4/0xcc0 kernel/workqueue.c:4241 __cancel_work_sync kernel/workqueue.c:4397 [inline] cancel_work_sync+0xd1/0xf0 kernel/workqueue.c:4434 smc_clcsock_release+0x5f/0xe0 net/smc/smc_close.c:29 __smc_release+0x5c2/0x880 net/smc/af_smc.c:304 smc_close_non_accepted+0xda/0x200 net/smc/af_smc.c:1855 smc_close_cleanup_listen net/smc/smc_close.c:45 [inline] smc_close_active+0xc3c/0x1070 net/smc/smc_close.c:225 __smc_release+0x634/0x880 net/smc/af_smc.c:280 smc_release+0x1fc/0x620 net/smc/af_smc.c:347 __sock_release+0xb3/0x270 net/socket.c:662 sock_close+0x1c/0x30 net/socket.c:1455 __fput+0x402/0xb70 fs/file_table.c:468 task_work_run+0x150/0x240 kernel/task_work.c:233 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline] __exit_to_user_mode_loop kernel/entry/common.c:44 [inline] exit_to_user_mode_loop+0xfb/0x540 kernel/entry/common.c:75 __exit_to_user_mode_prepare include/linux/irq-entry-common.h:226 [inline] syscall_exit_to_user_mode_prepare include/linux/irq-entry-common.h:256 [inline] syscall_exit_to_user_mode_work include/linux/entry-common.h:159 [inline] syscall_exit_to_user_mode include/linux/entry-common.h:194 [inline] do_syscall_64+0x4ee/0xf80 arch/x86/entry/syscall_64.c:100 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 *** 3 locks held by syz.2.7935/17968: #0: ffff88808070aa48 (&sb->s_type->i_mutex_key#13){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:1027 [inline] #0: ffff88808070aa48 (&sb->s_type->i_mutex_key#13){+.+.}-{4:4}, at: __sock_release+0x86/0x270 net/socket.c:661 #1: ffff888046afe660 (sk_lock-AF_SMC/1){+.+.}-{0:0}, at: smc_release+0x3a5/0x620 net/smc/af_smc.c:339 #2: ffffffff8e3c94a0 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline] #2: ffffffff8e3c94a0 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:867 [inline] #2: ffffffff8e3c94a0 (rcu_read_lock){....}-{1:3}, at: start_flush_work kernel/workqueue.c:4183 [inline] #2: ffffffff8e3c94a0 (rcu_read_lock){....}-{1:3}, at: __flush_work+0xfb/0xcc0 kernel/workqueue.c:4241 stack backtrace: CPU: 0 UID: 0 PID: 17968 Comm: syz.2.7935 Tainted: G U L syzkaller #0 PREEMPT(full) Tainted: [U]=USER, [L]=SOFTLOCKUP Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120 print_circular_bug+0x275/0x340 kernel/locking/lockdep.c:2043 check_noncircular+0x146/0x160 kernel/locking/lockdep.c:2175 check_prev_add kernel/locking/lockdep.c:3165 [inline] check_prevs_add kernel/locking/lockdep.c:3284 [inline] validate_chain kernel/locking/lockdep.c:3908 [inline] __lock_acquire+0x1669/0x2890 kernel/locking/lockdep.c:5237 lock_acquire kernel/locking/lockdep.c:5868 [inline] lock_acquire+0x179/0x330 kernel/locking/lockdep.c:5825 touch_work_lockdep_map kernel/workqueue.c:3955 [inline] start_flush_work kernel/workqueue.c:4209 [inline] __flush_work+0x4e4/0xcc0 kernel/workqueue.c:4241 __cancel_work_sync kernel/workqueue.c:4397 [inline] cancel_work_sync+0xd1/0xf0 kernel/workqueue.c:4434 smc_clcsock_release+0x5f/0xe0 net/smc/smc_close.c:29 __smc_release+0x5c2/0x880 net/smc/af_smc.c:304 smc_close_non_accepted+0xda/0x200 net/smc/af_smc.c:1855 smc_close_cleanup_listen net/smc/smc_close.c:45 [inline] smc_close_active+0xc3c/0x1070 net/smc/smc_close.c:225 __smc_release+0x634/0x880 net/smc/af_smc.c:280 smc_release+0x1fc/0x620 net/smc/af_smc.c:347 __sock_release+0xb3/0x270 net/socket.c:662 sock_close+0x1c/0x30 net/socket.c:1455 __fput+0x402/0xb70 fs/file_table.c:468 task_work_run+0x150/0x240 kernel/task_work.c:233 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline] __exit_to_user_mode_loop kernel/entry/common.c:44 [inline] exit_to_user_mode_loop+0xfb/0x540 kernel/entry/common.c:75 __exit_to_user_mode_prepare include/linux/irq-entry-common.h:226 [inline] syscall_exit_to_user_mode_prepare include/linux/irq-entry-common.h:256 [inline] syscall_exit_to_user_mode_work include/linux/entry-common.h:159 [inline] syscall_exit_to_user_mode include/linux/entry-common.h:194 [inline] do_syscall_64+0x4ee/0xf80 arch/x86/entry/syscall_64.c:100 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f89e8f8f7c9 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:00007ffc4c8ba6f8 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4 RAX: 0000000000000000 RBX: 00000000002e53f3 RCX: 00007f89e8f8f7c9 RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003 RBP: 00007f89e91e7da0 R08: 0000000000000001 R09: 000000134c8ba9ef R10: 0000001b2e120000 R11: 0000000000000246 R12: 00007f89e91e5fac R13: 00007f89e91e5fa0 R14: ffffffffffffffff R15: 00007ffc4c8ba810 EXT4-fs error (device sda1) in ext4_free_inode:361: Corrupt filesystem EXT4-fs error (device sda1) in ext4_free_inode:361: Corrupt filesystem EXT4-fs error (device sda1) in ext4_free_inode:361: Corrupt filesystem