audit: type=1400 audit(1661900694.801:140): avc:  denied  { mounton } for  pid=19991 comm="syz-executor336" path="/root/file0" dev="sda1" ino=1163 scontext=root:sysadm_r:sysadm_t tcontext=root:object_r:user_home_t tclass=dir permissive=1
============================================
WARNING: possible recursive locking detected
6.0.0-rc3-syzkaller #0 Not tainted
--------------------------------------------
kworker/0:18/4160 is trying to acquire lock:
ffff88810efe8418 (&clnt->lock){+.+.}-{2:2}, at: p9_req_put+0xd2/0x260

but task is already holding lock:
ffff88810efe8418 (&clnt->lock){+.+.}-{2:2}, at: p9_conn_cancel+0xb4/0xaa0

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/0:18/4160:
 #0: ffff888100067d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x8dd/0x1690
 #1: ffff88812f6bfd98 (p9_poll_work){+.+.}-{0:0}, at: process_one_work+0x913/0x1690
 #2: ffff88810efe8418 (&clnt->lock){+.+.}-{2:2}, at: p9_conn_cancel+0xb4/0xaa0

stack backtrace:
CPU: 0 PID: 4160 Comm: kworker/0:18 Not tainted 6.0.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
Workqueue: events p9_poll_workfn
Call Trace:
 <TASK>
 dump_stack_lvl+0x156/0x1cb
 dump_stack+0x15/0x1b
 __lock_acquire.cold+0x130/0x39c
 lock_acquire+0x21d/0x630
 _raw_spin_lock_irqsave+0x9b/0xf0
 p9_req_put+0xd2/0x260
 p9_client_cb+0x58/0x70
 p9_conn_cancel+0x6b9/0xaa0
 p9_poll_workfn+0x27c/0x570
 process_one_work+0x9e7/0x1690
 worker_thread+0x670/0x10b0
 kthread+0x302/0x3d0
 ret_from_fork+0x22/0x30
 </TASK>