============================================
WARNING: possible recursive locking detected
5.19.0-rc1-syzkaller-00214-gfe43c0188911 #0 Not tainted
--------------------------------------------
syz-executor138/3606 is trying to acquire lock:
ffff888078fe6068 (&pipe->mutex/1){+.+.}-{3:3}, at: __pipe_lock fs/pipe.c:103 [inline]
ffff888078fe6068 (&pipe->mutex/1){+.+.}-{3:3}, at: pipe_write+0x132/0x1bf0 fs/pipe.c:431

but task is already holding lock:
ffff888078fe6c68 (&pipe->mutex/1){+.+.}-{3:3}, at: pipe_lock_nested fs/pipe.c:82 [inline]
ffff888078fe6c68 (&pipe->mutex/1){+.+.}-{3:3}, at: pipe_lock+0x5a/0x70 fs/pipe.c:90

other info that might help us debug this:
 Possible unsafe locking scenario:

       CPU0
       ----
  lock(&pipe->mutex/1);
  lock(&pipe->mutex/1);

 *** DEADLOCK ***

 May be