======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.9.625/11084 is trying to acquire lock:
ffff888039e0c458 (&ima_iint_mutex_key[depth]){+.+.}-{4:4}, at: process_measurement+0x7e0/0x1c20 security/integrity/ima/ima_main.c:319

but task is already holding lock:
ffff888063f1c860 (&subsys->lock){+.+.}-{4:4}, at: nvmet_ns_enable+0x4d/0x780 drivers/nvme/target/core.c:583

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (&subsys->lock){+.+.}-{4:4}:
       __mutex_lock_common kernel/locking/rtmutex_api.c:559 [inline]
       mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:578
       nvmet_ns_device_path_store+0x54/0x160 drivers/nvme/target/configfs.c:536
       flush_write_buffer fs/configfs/file.c:207 [inline]
       configfs_write_iter+0x33a/0x430 fs/configfs/file.c:229
       new_sync_write fs/read_write.c:595 [inline]
       vfs_write+0x61e/0xbb0 fs/read_write.c:687
       ksys_write+0x156/0x270 fs/read_write.c:739
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 (&p->frag_sem){.+.+}-{4:4}:
       down_read+0x97/0x200 kernel/locking/rwsem.c:1574
       __configfs_open_file+0xd8/0x7d0 fs/configfs/file.c:304
       do_dentry_open+0x849/0x1420 fs/open.c:947
       vfs_open+0x3b/0x350 fs/open.c:1052
       dentry_open+0x61/0xa0 fs/open.c:1075
       ima_calc_file_hash+0x168/0x8a0 security/integrity/ima/ima_crypto.c:269
       ima_collect_measurement+0x521/0xa10 security/integrity/ima/ima_api.c:300
       process_measurement+0x1282/0x1c20 security/integrity/ima/ima_main.c:425
       ima_file_check+0xe1/0x130 security/integrity/ima/ima_main.c:685
       security_file_post_open+0xb3/0x260 security/security.c:2755
       do_open fs/namei.c:4702 [inline]
       path_openat+0x2eac/0x3850 fs/namei.c:4863
       do_file_open+0x23e/0x4a0 fs/namei.c:4892
       do_sys_openat2+0x115/0x200 fs/open.c:1368
       do_sys_open fs/open.c:1374 [inline]
       __do_sys_openat fs/open.c:1390 [inline]
       __se_sys_openat fs/open.c:1385 [inline]
       __x64_sys_openat+0x138/0x170 fs/open.c:1385
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&ima_iint_mutex_key[depth]){+.+.}-{4:4}:
       check_prev_add kernel/locking/lockdep.c:3165 [inline]
       check_prevs_add kernel/locking/lockdep.c:3284 [inline]
       validate_chain kernel/locking/lockdep.c:3908 [inline]
       __lock_acquire+0x1520/0x2ce0 kernel/locking/lockdep.c:5237
       lock_acquire+0x106/0x350 kernel/locking/lockdep.c:5868
       __mutex_lock_common kernel/locking/rtmutex_api.c:559 [inline]
       mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:578
       process_measurement+0x7e0/0x1c20 security/integrity/ima/ima_main.c:319
       ima_file_check+0xe1/0x130 security/integrity/ima/ima_main.c:685
       security_file_post_open+0xb3/0x260 security/security.c:2755
       do_open fs/namei.c:4702 [inline]
       path_openat+0x2eac/0x3850 fs/namei.c:4863
       do_file_open+0x23e/0x4a0 fs/namei.c:4892
       file_open_name fs/open.c:1326 [inline]
       filp_open+0x16d/0x1d0 fs/open.c:1343
       nvmet_file_ns_enable+0x74/0x360 drivers/nvme/target/io-cmd-file.c:41
       nvmet_ns_enable+0xaa/0x780 drivers/nvme/target/core.c:596
       nvmet_ns_enable_store+0xd7/0x170 drivers/nvme/target/configfs.c:735
       flush_write_buffer fs/configfs/file.c:207 [inline]
       configfs_write_iter+0x33a/0x430 fs/configfs/file.c:229
       new_sync_write fs/read_write.c:595 [inline]
       vfs_write+0x61e/0xbb0 fs/read_write.c:687
       ksys_write+0x156/0x270 fs/read_write.c:739
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

other info that might help us debug this:

Chain exists of:
  &ima_iint_mutex_key[depth] --> &p->frag_sem --> &subsys->lock

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&subsys->lock);
                               lock(&p->frag_sem);
                               lock(&subsys->lock);
  lock(&ima_iint_mutex_key[depth]);

 *** DEADLOCK ***

6 locks held by syz.9.625/11084:
 #0: ffff888037535328 (&f->f_pos_lock){+.+.}-{4:4}, at: fdget_pos+0x252/0x320 fs/file.c:1259
 #1: ffff88801bf28500 (sb_writers#25){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:2733 [inline]
 #1: ffff88801bf28500 (sb_writers#25){.+.+}-{0:0}, at: vfs_write+0x231/0xbb0 fs/read_write.c:683
 #2: ffff888035550c78 (&buffer->mutex){+.+.}-{4:4}, at: configfs_write_iter+0x81/0x430 fs/configfs/file.c:226
 #3: ffff888030abe568 (&p->frag_sem){.+.+}-{4:4}, at: flush_write_buffer fs/configfs/file.c:205 [inline]
 #3: ffff888030abe568 (&p->frag_sem){.+.+}-{4:4}, at: configfs_write_iter+0x23b/0x430 fs/configfs/file.c:229
 #4: ffffffff8ec4e560 (nvmet_config_sem){+.+.}-{4:4}, at: nvmet_ns_enable_store+0xc8/0x170 drivers/nvme/target/configfs.c:733
 #5: ffff888063f1c860 (&subsys->lock){+.+.}-{4:4}, at: nvmet_ns_enable+0x4d/0x780 drivers/nvme/target/core.c:583

stack backtrace:
CPU: 0 UID: 0 PID: 11084 Comm: syz.9.625 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 print_circular_bug+0x2e1/0x300 kernel/locking/lockdep.c:2043
 check_noncircular+0x12e/0x150 kernel/locking/lockdep.c:2175
 check_prev_add kernel/locking/lockdep.c:3165 [inline]
 check_prevs_add kernel/locking/lockdep.c:3284 [inline]
 validate_chain kernel/locking/lockdep.c:3908 [inline]
 __lock_acquire+0x1520/0x2ce0 kernel/locking/lockdep.c:5237
 lock_acquire+0x106/0x350 kernel/locking/lockdep.c:5868
 __mutex_lock_common kernel/locking/rtmutex_api.c:559 [inline]
 mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:578
 process_measurement+0x7e0/0x1c20 security/integrity/ima/ima_main.c:319
 ima_file_check+0xe1/0x130 security/integrity/ima/ima_main.c:685
 security_file_post_open+0xb3/0x260 security/security.c:2755
 do_open fs/namei.c:4702 [inline]
 path_openat+0x2eac/0x3850 fs/namei.c:4863
 do_file_open+0x23e/0x4a0 fs/namei.c:4892
 file_open_name fs/open.c:1326 [inline]
 filp_open+0x16d/0x1d0 fs/open.c:1343
 nvmet_file_ns_enable+0x74/0x360 drivers/nvme/target/io-cmd-file.c:41
 nvmet_ns_enable+0xaa/0x780 drivers/nvme/target/core.c:596
 nvmet_ns_enable_store+0xd7/0x170 drivers/nvme/target/configfs.c:735
 flush_write_buffer fs/configfs/file.c:207 [inline]
 configfs_write_iter+0x33a/0x430 fs/configfs/file.c:229
 new_sync_write fs/read_write.c:595 [inline]
 vfs_write+0x61e/0xbb0 fs/read_write.c:687
 ksys_write+0x156/0x270 fs/read_write.c:739
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f5b2fe8e0d9
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:00007f5b2e0e6028 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f5b30115fa0 RCX: 00007f5b2fe8e0d9
RDX: 0000000000000001 RSI: 0000200000000580 RDI: 0000000000000006
RBP: 00007f5b2ff25024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f5b30116038 R14: 00007f5b30115fa0 R15: 00007fff0ec2e238
 </TASK>