======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.1.2395/15315 is trying to acquire lock:
ffff888110e57ae8 ((work_completion)(&new_smc->smc_listen_work)){+.+.}-{0:0}, at: __flush_work+0x101/0xca0

but task is already holding lock:
ffff888035cd27e0 (sk_lock-AF_SMC/1){+.+.}-{0:0}, at: smc_release+0x24d/0x550

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
       smc_listen_out+0xd4/0x3d0
       smc_listen_work+0x81d/0x1410
       process_scheduled_works+0xa88/0x14c0
       worker_thread+0xa47/0xfb0
       kthread+0x38b/0x480
       ret_from_fork+0x514/0xb70
       ret_from_fork_asm+0x1a/0x30

-> #0 ((work_completion)(&new_smc->smc_listen_work)){+.+.}-{0:0}:
       __lock_acquire+0x1520/0x2cf0
       lock_acquire+0x106/0x350
       __flush_work+0x74c/0xca0
       __cancel_work_sync+0xbf/0x110
       smc_clcsock_release+0x60/0xf0
       __smc_release+0x64e/0x7c0
       smc_close_non_accepted+0xd5/0x1f0
       smc_close_active+0xb42/0xf30
       __smc_release+0x9c/0x7c0
       smc_release+0x2c5/0x550
       __sock_release+0xa0/0x1f0
       sock_close+0x1c/0x30
       __fput+0x418/0xa50
       task_work_run+0x1d9/0x270
       do_exit+0x73a/0x2360
       do_group_exit+0x22d/0x2f0
       get_signal+0x121b/0x12c0
       arch_do_signal_or_restart+0xbb/0x860
       exit_to_user_mode_loop+0x10e/0x770
       do_syscall_64+0x328/0x520
       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.1.2395/15315: 3, last CPU#0:
 #0: ffff888027b44a40 (&sb->s_type->i_mutex_key#13){+.+.}-{4:4}, at: __sock_release+0x7a/0x1f0
 #1: ffff888035cd27e0 (sk_lock-AF_SMC/1){+.+.}-{0:0}, at: smc_release+0x24d/0x550
 #2: ffffffff8eb5a1e0 (rcu_read_lock){....}-{1:3}, at: __flush_work+0x101/0xca0

stack backtrace:
CPU: 0 UID: 0 PID: 15315 Comm: syz.1.2395 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150
 print_circular_bug+0x2e1/0x300
 check_noncircular+0x12e/0x150
 __lock_acquire+0x1520/0x2cf0
 lock_acquire+0x106/0x350
 __flush_work+0x74c/0xca0
 __cancel_work_sync+0xbf/0x110
 smc_clcsock_release+0x60/0xf0
 __smc_release+0x64e/0x7c0
 smc_close_non_accepted+0xd5/0x1f0
 smc_close_active+0xb42/0xf30
 __smc_release+0x9c/0x7c0
 smc_release+0x2c5/0x550
 __sock_release+0xa0/0x1f0
 sock_close+0x1c/0x30
 __fput+0x418/0xa50
 task_work_run+0x1d9/0x270
 do_exit+0x73a/0x2360
 do_group_exit+0x22d/0x2f0
 get_signal+0x121b/0x12c0
 arch_do_signal_or_restart+0xbb/0x860
 exit_to_user_mode_loop+0x10e/0x770
 do_syscall_64+0x328/0x520
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fdf4559e0d9
Code: Unable to access opcode bytes at 0x7fdf4559e0af.
RSP: 002b:00007fdf4653d0e8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: 0000000000000001 RBX: 00007fdf45825fa8 RCX: 00007fdf4559e0d9
RDX: 00000000000f4240 RSI: 0000000000000081 RDI: 00007fdf45825fac
RBP: 00007fdf45825fa0 R08: 3fffffffffffffff R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fdf45826038 R14: 00007ffda3865240 R15: 00007ffda3865328
 </TASK>
