nvmet: adding nsid 1 to subsystem testsubsys
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.6.2854/12536 is trying to acquire lock:
ffff8881202ae460 (sb_writers#5){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90

but task is already holding lock:
ffff8881012f0068 (&subsys->lock){+.+.}-{4:4}, at: nvmet_ns_enable+0x4d/0x780

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #4 (&subsys->lock){+.+.}-{4:4}:
       __mutex_lock+0x19d/0x1550
       nvmet_ns_buffered_io_store+0xe1/0x200
       configfs_write_iter+0x337/0x430
       vfs_write+0x612/0xba0
       ksys_write+0x150/0x270
       do_syscall_64+0x166/0x520
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #3 (&p->frag_sem){.+.+}-{4:4}:
       down_read+0x4a/0x330
       configfs_read_iter+0x1cc/0x620
       __kernel_read+0x4ca/0x960
       integrity_kernel_read+0x89/0xd0
       ima_calc_file_hash+0x451/0x890
       ima_collect_measurement+0x51b/0xa00
       process_measurement+0x1272/0x1c10
       ima_file_check+0xe1/0x130
       security_file_post_open+0xb3/0x260
       path_openat+0x1485/0x1d60
       do_file_open+0x23e/0x4a0
       do_sys_openat2+0x115/0x200
       __x64_sys_openat+0x138/0x170
       do_syscall_64+0x166/0x520
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #2 (&buffer->mutex#2){+.+.}-{4:4}:
       __mutex_lock+0x19d/0x1550
       configfs_read_iter+0x70/0x620
       __kernel_read+0x4ca/0x960
       integrity_kernel_read+0x89/0xd0
       ima_calc_file_hash+0x451/0x890
       ima_collect_measurement+0x51b/0xa00
       process_measurement+0x1272/0x1c10
       ima_file_check+0xe1/0x130
       security_file_post_open+0xb3/0x260
       path_openat+0x1485/0x1d60
       do_file_open+0x23e/0x4a0
       do_sys_openat2+0x115/0x200
       __x64_sys_openat+0x138/0x170
       do_syscall_64+0x166/0x520
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 (&ima_iint_mutex_key[depth]){+.+.}-{4:4}:
       __mutex_lock+0x19d/0x1550
       ima_file_truncate+0xb6/0x170
       security_file_truncate+0x118/0x240
       path_openat+0x1569/0x1d60
       do_file_open+0x23e/0x4a0
       do_sys_openat2+0x115/0x200
       __x64_sys_openat+0x138/0x170
       do_syscall_64+0x166/0x520
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (sb_writers#5){.+.+}-{0:0}:
       __lock_acquire+0x1520/0x2cf0
       lock_acquire+0x106/0x350
       sb_start_write+0x4d/0x1d0
       mnt_want_write+0x41/0x90
       lookup_open+0x1e6/0x1a40
       path_openat+0x677/0x1d60
       do_file_open+0x23e/0x4a0
       filp_open+0x16d/0x1d0
       nvmet_file_ns_enable+0x74/0x350
       nvmet_ns_enable+0xaa/0x780
       nvmet_ns_enable_store+0xd7/0x170
       configfs_write_iter+0x337/0x430
       vfs_write+0x612/0xba0
       ksys_write+0x150/0x270
       do_syscall_64+0x166/0x520
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

other info that might help us debug this:

Chain exists of:
  sb_writers#5 --> &p->frag_sem --> &subsys->lock

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&subsys->lock);
                               lock(&p->frag_sem);
                               lock(&subsys->lock);
  rlock(sb_writers#5);

 *** DEADLOCK ***

locks held by syz.6.2854/12536: 6, last CPU#0:
 #0: ffff8881137274f0 (&f->f_pos_lock){+.+.}-{4:4}, at: fdget_pos+0x246/0x320
 #1: ffff888101bbe460 (sb_writers#31){.+.+}-{0:0}, at: vfs_write+0x22b/0xba0
 #2: ffff888101ba2680 (&buffer->mutex#2){+.+.}-{4:4}, at: configfs_write_iter+0x7e/0x430
 #3: ffff88810e830270 (&p->frag_sem){.+.+}-{4:4}, at: configfs_write_iter+0x238/0x430
 #4: ffffffff8f6d5b88 (nvmet_config_sem){+.+.}-{4:4}, at: nvmet_ns_enable_store+0xc8/0x170
 #5: ffff8881012f0068 (&subsys->lock){+.+.}-{4:4}, at: nvmet_ns_enable+0x4d/0x780

stack backtrace:
CPU: 0 UID: 0 PID: 12536 Comm: syz.6.2854 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150
 print_circular_bug+0x2e1/0x300
 check_noncircular+0x12e/0x150
 __lock_acquire+0x1520/0x2cf0
 lock_acquire+0x106/0x350
 sb_start_write+0x4d/0x1d0
 mnt_want_write+0x41/0x90
 lookup_open+0x1e6/0x1a40
 path_openat+0x677/0x1d60
 do_file_open+0x23e/0x4a0
 filp_open+0x16d/0x1d0
 nvmet_file_ns_enable+0x74/0x350
 nvmet_ns_enable+0xaa/0x780
 nvmet_ns_enable_store+0xd7/0x170
 configfs_write_iter+0x337/0x430
 vfs_write+0x612/0xba0
 ksys_write+0x150/0x270
 do_syscall_64+0x166/0x520
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fb0a7d9e159
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fb0a8c79028 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fb0a8025fa0 RCX: 00007fb0a7d9e159
RDX: 0000000000000001 RSI: 00002000000004c0 RDI: 0000000000000004
RBP: 00007fb0a7e3506b R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fb0a8026038 R14: 00007fb0a8025fa0 R15: 00007ffce4f4b9c8
 </TASK>
nvmet: failed to open file ./file: (-2)
