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

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

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

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

 *** DEADLOCK ***