======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.6.414/8450 is trying to acquire lock:
ffff0000d64a1688 ((work_completion)(&new_smc->smc_listen_work)){+.+.}-{0:0}, at: touch_work_lockdep_map+0x70/0x118 kernel/workqueue.c:3949

but task is already holding lock:
ffff0000d64a0260 (sk_lock-AF_SMC/1){+.+.}-{0:0}, at: smc_release+0x1e8/0x534 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+0x58/0x118 net/core/sock.c:3720
       smc_listen_out+0x114/0x3b0 net/smc/af_smc.c:1924
       smc_listen_out_connected net/smc/af_smc.c:1944 [inline]
       smc_listen_work+0x1d0/0xf38 net/smc/af_smc.c:-1
       process_one_work+0x7e8/0x155c kernel/workqueue.c:3263
       process_scheduled_works kernel/workqueue.c:3346 [inline]
       worker_thread+0x958/0xed8 kernel/workqueue.c:3427
       kthread+0x5fc/0x75c kernel/kthread.c:463
       ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:844

-> #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+0x1774/0x30a4 kernel/locking/lockdep.c:5237
       lock_acquire+0x14c/0x2e0 kernel/locking/lockdep.c:5868
       touch_work_lockdep_map+0x98/0x118 kernel/workqueue.c:3951
       start_flush_work kernel/workqueue.c:4205 [inline]
       __flush_work+0x4fc/0x8c0 kernel/workqueue.c:4237
       __cancel_work_sync kernel/workqueue.c:4393 [inline]
       cancel_work_sync+0xc4/0x120 kernel/workqueue.c:4430
       smc_clcsock_release+0x64/0xe8 net/smc/smc_close.c:29
       __smc_release+0x568/0x6c4 net/smc/af_smc.c:304
       smc_close_non_accepted+0xd8/0x260 net/smc/af_smc.c:1855
       smc_close_cleanup_listen net/smc/smc_close.c:45 [inline]
       smc_close_active+0x954/0xcc8 net/smc/smc_close.c:225
       __smc_release+0x48c/0x6c4 net/smc/af_smc.c:280
       smc_release+0x258/0x534 net/smc/af_smc.c:347
       __sock_release net/socket.c:662 [inline]
       sock_close+0xa0/0x1e4 net/socket.c:1455
       __fput+0x340/0x75c fs/file_table.c:468
       ____fput+0x20/0x58 fs/file_table.c:496
       task_work_run+0x1dc/0x260 kernel/task_work.c:227
       resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
       exit_to_user_mode_loop+0xfc/0x178 kernel/entry/common.c:43
       exit_to_user_mode_prepare include/linux/irq-entry-common.h:225 [inline]
       arm64_exit_to_user_mode arch/arm64/kernel/entry-common.c:103 [inline]
       el0_svc+0x170/0x254 arch/arm64/kernel/entry-common.c:747
       el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:765
       el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:596

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.6.414/8450:
 #0: ffff0000ff234cc8 (&sb->s_type->i_mutex_key#11){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:980 [inline]
 #0: ffff0000ff234cc8 (&sb->s_type->i_mutex_key#11){+.+.}-{4:4}, at: __sock_release net/socket.c:661 [inline]
 #0: ffff0000ff234cc8 (&sb->s_type->i_mutex_key#11){+.+.}-{4:4}, at: sock_close+0x7c/0x1e4 net/socket.c:1455
 #1: ffff0000d64a0260 (sk_lock-AF_SMC/1){+.+.}-{0:0}, at: smc_release+0x1e8/0x534 net/smc/af_smc.c:-1
 #2: ffff80008f76b5a0 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire+0x10/0x4c include/linux/rcupdate.h:330

stack backtrace:
CPU: 1 UID: 0 PID: 8450 Comm: syz.6.414 Not tainted syzkaller #0 PREEMPT 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/03/2025
Call trace:
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:499 (C)
 __dump_stack+0x30/0x40 lib/dump_stack.c:94
 dump_stack_lvl+0xd8/0x12c lib/dump_stack.c:120
 dump_stack+0x1c/0x28 lib/dump_stack.c:129
 print_circular_bug+0x324/0x32c kernel/locking/lockdep.c:2043
 check_noncircular+0x154/0x174 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+0x1774/0x30a4 kernel/locking/lockdep.c:5237
 lock_acquire+0x14c/0x2e0 kernel/locking/lockdep.c:5868
 touch_work_lockdep_map+0x98/0x118 kernel/workqueue.c:3951
 start_flush_work kernel/workqueue.c:4205 [inline]
 __flush_work+0x4fc/0x8c0 kernel/workqueue.c:4237
 __cancel_work_sync kernel/workqueue.c:4393 [inline]
 cancel_work_sync+0xc4/0x120 kernel/workqueue.c:4430
 smc_clcsock_release+0x64/0xe8 net/smc/smc_close.c:29
 __smc_release+0x568/0x6c4 net/smc/af_smc.c:304
 smc_close_non_accepted+0xd8/0x260 net/smc/af_smc.c:1855
 smc_close_cleanup_listen net/smc/smc_close.c:45 [inline]
 smc_close_active+0x954/0xcc8 net/smc/smc_close.c:225
 __smc_release+0x48c/0x6c4 net/smc/af_smc.c:280
 smc_release+0x258/0x534 net/smc/af_smc.c:347
 __sock_release net/socket.c:662 [inline]
 sock_close+0xa0/0x1e4 net/socket.c:1455
 __fput+0x340/0x75c fs/file_table.c:468
 ____fput+0x20/0x58 fs/file_table.c:496
 task_work_run+0x1dc/0x260 kernel/task_work.c:227
 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
 exit_to_user_mode_loop+0xfc/0x178 kernel/entry/common.c:43
 exit_to_user_mode_prepare include/linux/irq-entry-common.h:225 [inline]
 arm64_exit_to_user_mode arch/arm64/kernel/entry-common.c:103 [inline]
 el0_svc+0x170/0x254 arch/arm64/kernel/entry-common.c:747
 el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:765
 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:596