netdevsim netdevsim0 netdevsim2: set [1, 0] type 2 family 0 port 6081 - 0 netdevsim netdevsim0 netdevsim3: set [1, 0] type 2 family 0 port 6081 - 0 ====================================================== WARNING: possible circular locking dependency detected 5.15.182-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor149/4025 is trying to acquire lock: ffff0000c8451450 ((work_completion)(&new_smc->smc_listen_work)){+.+.}-{0:0}, at: __flush_work+0xcc/0x1bc kernel/workqueue.c:3087 but task is already holding lock: ffff0000c8450120 (sk_lock-AF_SMC/1){+.+.}-{0:0}, at: smc_release+0x1f4/0x568 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+0xd8/0x1d4 net/core/sock.c:3251 smc_listen_out+0x11c/0x3e8 net/smc/af_smc.c:1524 smc_listen_out_connected net/smc/af_smc.c:1544 [inline] smc_listen_work+0x1d0/0xd2c net/smc/af_smc.c:-1 process_one_work+0x79c/0x1140 kernel/workqueue.c:2310 worker_thread+0x8f4/0x101c kernel/workqueue.c:2457 kthread+0x374/0x454 kernel/kthread.c:334 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870 -> #0 ((work_completion)(&new_smc->smc_listen_work)){+.+.}-{0:0}: check_prev_add kernel/locking/lockdep.c:3053 [inline] check_prevs_add kernel/locking/lockdep.c:3172 [inline] validate_chain kernel/locking/lockdep.c:3788 [inline] __lock_acquire+0x2928/0x651c kernel/locking/lockdep.c:5012 lock_acquire+0x1f4/0x620 kernel/locking/lockdep.c:5623 __flush_work+0xf4/0x1bc kernel/workqueue.c:3090 __cancel_work_timer+0x2ec/0x448 kernel/workqueue.c:3181 cancel_work_sync+0x24/0x38 kernel/workqueue.c:3217 smc_clcsock_release+0x64/0xe8 net/smc/smc_close.c:29 __smc_release+0x3bc/0x530 net/smc/af_smc.c:211 smc_close_non_accepted+0xdc/0x298 net/smc/af_smc.c:1466 smc_close_cleanup_listen net/smc/smc_close.c:45 [inline] smc_close_active+0x890/0xc20 net/smc/smc_close.c:219 __smc_release+0x2dc/0x530 net/smc/af_smc.c:187 smc_release+0x264/0x568 net/smc/af_smc.c:254 __sock_release net/socket.c:649 [inline] sock_close+0xb4/0x1f8 net/socket.c:1336 __fput+0x1c0/0x7f8 fs/file_table.c:311 ____fput+0x20/0x30 fs/file_table.c:339 task_work_run+0x12c/0x1e0 kernel/task_work.c:188 exit_task_work include/linux/task_work.h:33 [inline] do_exit+0x67c/0x1f58 kernel/exit.c:874 do_group_exit+0x100/0x268 kernel/exit.c:996 __do_sys_exit_group kernel/exit.c:1007 [inline] __se_sys_exit_group kernel/exit.c:1005 [inline] __wake_up_parent+0x0/0x60 kernel/exit.c:1005 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181 el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608 el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584 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-executor149/4025: #0: ffff0000e209d010 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline] #0: ffff0000e209d010 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: __sock_release net/socket.c:648 [inline] #0: ffff0000e209d010 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: sock_close+0x7c/0x1f8 net/socket.c:1336 #1: ffff0000c8450120 (sk_lock-AF_SMC/1){+.+.}-{0:0}, at: smc_release+0x1f4/0x568 net/smc/af_smc.c:-1 stack backtrace: CPU: 0 PID: 4025 Comm: syz-executor149 Not tainted 5.15.182-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/19/2025 Call trace: dump_backtrace+0x0/0x43c arch/arm64/kernel/stacktrace.c:152 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216 __dump_stack+0x30/0x40 lib/dump_stack.c:88 dump_stack_lvl+0xf8/0x160 lib/dump_stack.c:106 dump_stack+0x1c/0x5c lib/dump_stack.c:113 print_circular_bug+0x148/0x1b0 kernel/locking/lockdep.c:2011 check_noncircular+0x240/0x2d4 kernel/locking/lockdep.c:2133 check_prev_add kernel/locking/lockdep.c:3053 [inline] check_prevs_add kernel/locking/lockdep.c:3172 [inline] validate_chain kernel/locking/lockdep.c:3788 [inline] __lock_acquire+0x2928/0x651c kernel/locking/lockdep.c:5012 lock_acquire+0x1f4/0x620 kernel/locking/lockdep.c:5623 __flush_work+0xf4/0x1bc kernel/workqueue.c:3090 __cancel_work_timer+0x2ec/0x448 kernel/workqueue.c:3181 cancel_work_sync+0x24/0x38 kernel/workqueue.c:3217 smc_clcsock_release+0x64/0xe8 net/smc/smc_close.c:29 __smc_release+0x3bc/0x530 net/smc/af_smc.c:211 smc_close_non_accepted+0xdc/0x298 net/smc/af_smc.c:1466 smc_close_cleanup_listen net/smc/smc_close.c:45 [inline] smc_close_active+0x890/0xc20 net/smc/smc_close.c:219 __smc_release+0x2dc/0x530 net/smc/af_smc.c:187 smc_release+0x264/0x568 net/smc/af_smc.c:254 __sock_release net/socket.c:649 [inline] sock_close+0xb4/0x1f8 net/socket.c:1336 __fput+0x1c0/0x7f8 fs/file_table.c:311 ____fput+0x20/0x30 fs/file_table.c:339 task_work_run+0x12c/0x1e0 kernel/task_work.c:188 exit_task_work include/linux/task_work.h:33 [inline] do_exit+0x67c/0x1f58 kernel/exit.c:874 do_group_exit+0x100/0x268 kernel/exit.c:996 __do_sys_exit_group kernel/exit.c:1007 [inline] __se_sys_exit_group kernel/exit.c:1005 [inline] __wake_up_parent+0x0/0x60 kernel/exit.c:1005 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181 el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608 el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584