DUID 00:04:11:31:ea:d8:bb:db:47:a8:80:cb:7d:0b:3c:d8:ea:74
forked to background, child pid 3189
[   25.532222][ T3190] 8021q: adding VLAN 0 to HW filter on device bond0
[   25.542867][ T3190] eql: remember to turn off Van-Jacobson compression on your slave devices
Starting sshd: OK

syzkaller
Warning: Permanently added '10.128.10.6' (ECDSA) to the list of known hosts.
syzkaller login: [   47.374484][ T3606] 
[   47.374493][ T3606] ============================================
[   47.374499][ T3606] WARNING: possible recursive locking detected
[   47.374504][ T3606] 5.19.0-rc1-syzkaller-00214-gfe43c0188911 #0 Not tainted
[   47.374512][ T3606] --------------------------------------------
[   47.374516][ T3606] syz-executor138/3606 is trying to acquire lock:
[   47.374526][ T3606] ffff888078fe6068 (&pipe->mutex/1){+.+.}-{3:3}, at: pipe_write+0x132/0x1bf0
[   47.374567][ T3606] 
[   47.374567][ T3606] but task is already holding lock:
[   47.374569][ T3606] ffff888078fe6c68 (&pipe->mutex/1){+.+.}-{3:3}, at: pipe_lock+0x5a/0x70
[   47.374598][ T3606] 
[   47.374598][ T3606] other info that might help us debug this:
[   47.374601][ T3606]  Possible unsafe locking scenario:
[   47.374601][ T3606] 
[   47.374603][ T3606]        CPU0
[   47.374605][ T3606]        ----
[   47.374607][ T3606]   lock(&pipe->mutex/1);
[   47.374616][ T3606]   lock(&pipe->mutex/1);
[   47.374624][ T3606] 
[   47.374624][ T3606]  *** DEADLOCK ***
[   47.374624][ T3606] 
[   47.374627][ T3606]  May be