============================================
WARNING: possible recursive locking detected
5.19.0-rc8-next-20220728 #1 Not tainted
--------------------------------------------
kworker/1:1/24 is trying to acquire lock:
ffff88800f85b818 (&clnt->lock){+.+.}-{2:2}, at: p9_req_put+0xca/0x250

but task is already holding lock:
ffff88800f85b818 (&clnt->lock){+.+.}-{2:2}, at: p9_conn_cancel+0xa2/0x7c0

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

       CPU0
       ----
  lock(&clnt->lock);
  lock(&clnt->lock);

 *** DEADLOCK ***

 May be due to missing lock nesting notation

3 locks held by kworker/1:1/24:
 #0: ffff888007c58d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x90d/0x1690
 #1: ffff88800881fdb0 (p9_poll_work){+.+.}-{0:0}, at: process_one_work+0x941/0x1690
 #2: ffff88800f85b818 (&clnt->lock){+.+.}-{2:2}, at: p9_conn_cancel+0xa2/0x7c0

stack backtrace:
CPU: 1 PID: 24 Comm: kworker/1:1 Not tainted 5.19.0-rc8-next-20220728 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014
Workqueue: events p9_poll_workfn
Call Trace:
 <TASK>
 dump_stack_lvl+0x8b/0xb3
 __lock_acquire.cold+0x178/0x3bd
 lock_acquire+0x1a2/0x530
 _raw_spin_lock_irqsave+0x39/0x60
 p9_req_put+0xca/0x250
 p9_conn_cancel+0x4ca/0x7c0
 p9_poll_workfn+0x21e/0x480
 process_one_work+0xa0f/0x1690
 worker_thread+0x637/0x1260
 kthread+0x2ed/0x3a0
 ret_from_fork+0x22/0x30
 </TASK>