====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.1.532/6051 is trying to acquire lock: ffff0000d96539c0 (&iint_mutex_key[depth]#2){+.+.}-{3:3}, at: process_measurement+0x3a8/0x17fc security/integrity/ima/ima_main.c:261 but task is already holding lock: ffff0000d9356870 (&subsys->lock#2){+.+.}-{3:3}, at: nvmet_ns_enable+0x5c/0x724 drivers/nvme/target/core.c:559 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&subsys->lock#2){+.+.}-{3:3}: __mutex_lock_common+0x1a0/0x1f3c kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799 nvmet_ns_buffered_io_store+0xdc/0x1dc drivers/nvme/target/configfs.c:572 flush_write_buffer fs/configfs/file.c:207 [inline] configfs_write_iter+0x260/0x338 fs/configfs/file.c:229 call_write_iter include/linux/fs.h:2271 [inline] new_sync_write fs/read_write.c:491 [inline] vfs_write+0x3c8/0x7c8 fs/read_write.c:584 ksys_write+0x12c/0x228 fs/read_write.c:637 __do_sys_write fs/read_write.c:649 [inline] __se_sys_write fs/read_write.c:646 [inline] __arm64_sys_write+0x7c/0x90 fs/read_write.c:646 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x290 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x13c/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x5c/0x134 arch/arm64/kernel/syscall.c:204 el0_svc+0x58/0x12c arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585 -> #1 (&p->frag_sem){.+.+}-{3:3}: down_read+0x64/0x300 kernel/locking/rwsem.c:1520 __configfs_open_file+0xd4/0x68c fs/configfs/file.c:304 configfs_open_file+0x2c/0x3c fs/configfs/file.c:393 do_dentry_open+0x738/0xf8c fs/open.c:882 vfs_open fs/open.c:1015 [inline] dentry_open+0xc8/0x130 fs/open.c:1031 ima_calc_file_hash+0x14c/0x1560 security/integrity/ima/ima_crypto.c:558 ima_collect_measurement+0x410/0x950 security/integrity/ima/ima_api.c:293 process_measurement+0xdd0/0x17fc security/integrity/ima/ima_main.c:351 ima_file_check+0xcc/0x118 security/integrity/ima/ima_main.c:534 do_open fs/namei.c:3679 [inline] path_openat+0x2050/0x27a0 fs/namei.c:3834 do_filp_open+0x198/0x38c fs/namei.c:3861 do_sys_openat2+0x134/0x3fc fs/open.c:1320 do_sys_open fs/open.c:1336 [inline] __do_sys_openat fs/open.c:1352 [inline] __se_sys_openat fs/open.c:1347 [inline] __arm64_sys_openat+0x11c/0x150 fs/open.c:1347 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x290 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x13c/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x5c/0x134 arch/arm64/kernel/syscall.c:204 el0_svc+0x58/0x12c arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585 -> #0 (&iint_mutex_key[depth]#2){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3162 [inline] check_prevs_add kernel/locking/lockdep.c:3281 [inline] validate_chain kernel/locking/lockdep.c:3897 [inline] __lock_acquire+0x3504/0x7280 kernel/locking/lockdep.c:5171 lock_acquire+0x210/0x63c kernel/locking/lockdep.c:5790 __mutex_lock_common+0x1a0/0x1f3c kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799 process_measurement+0x3a8/0x17fc security/integrity/ima/ima_main.c:261 ima_file_check+0xcc/0x118 security/integrity/ima/ima_main.c:534 do_open fs/namei.c:3679 [inline] path_openat+0x2050/0x27a0 fs/namei.c:3834 do_filp_open+0x198/0x38c fs/namei.c:3861 file_open_name fs/open.c:1265 [inline] filp_open+0x160/0x1cc fs/open.c:1285 nvmet_file_ns_enable+0x88/0x2f8 drivers/nvme/target/io-cmd-file.c:41 nvmet_ns_enable+0xe4/0x724 drivers/nvme/target/core.c:576 nvmet_ns_enable_store+0xd4/0x170 drivers/nvme/target/configfs.c:548 flush_write_buffer fs/configfs/file.c:207 [inline] configfs_write_iter+0x260/0x338 fs/configfs/file.c:229 call_write_iter include/linux/fs.h:2271 [inline] new_sync_write fs/read_write.c:491 [inline] vfs_write+0x3c8/0x7c8 fs/read_write.c:584 ksys_write+0x12c/0x228 fs/read_write.c:637 __do_sys_write fs/read_write.c:649 [inline] __se_sys_write fs/read_write.c:646 [inline] __arm64_sys_write+0x7c/0x90 fs/read_write.c:646 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x290 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x13c/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x5c/0x134 arch/arm64/kernel/syscall.c:204 el0_svc+0x58/0x12c arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585 other info that might help us debug this: Chain exists of: &iint_mutex_key[depth]#2 --> &p->frag_sem --> &subsys->lock#2 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&subsys->lock#2); lock(&p->frag_sem); lock(&subsys->lock#2); lock(&iint_mutex_key[depth]#2); *** DEADLOCK *** 6 locks held by syz.1.532/6051: #0: ffff0000c32f39e8 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x118/0x17c fs/file.c:1038 #1: ffff0000c71c8460 (sb_writers#14){.+.+}-{0:0}, at: vfs_write+0x254/0x7c8 fs/read_write.c:580 #2: ffff0000d213b288 (&buffer->mutex){+.+.}-{3:3}, at: configfs_write_iter+0x74/0x338 fs/configfs/file.c:226 #3: ffff0000d213a078 (&p->frag_sem){.+.+}-{3:3}, at: flush_write_buffer fs/configfs/file.c:205 [inline] #3: ffff0000d213a078 (&p->frag_sem){.+.+}-{3:3}, at: configfs_write_iter+0x1a8/0x338 fs/configfs/file.c:229 #4: ffff800016b19450 (nvmet_config_sem){+.+.}-{3:3}, at: nvmet_ns_enable_store+0xc4/0x170 drivers/nvme/target/configfs.c:546 #5: ffff0000d9356870 (&subsys->lock#2){+.+.}-{3:3}, at: nvmet_ns_enable+0x5c/0x724 drivers/nvme/target/core.c:559 stack backtrace: CPU: 0 PID: 6051 Comm: syz.1.532 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/23/2026 Call trace: dump_backtrace+0x1c4/0x1f0 arch/arm64/kernel/stacktrace.c:158 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165 __dump_stack+0x30/0x40 lib/dump_stack.c:88 dump_stack_lvl+0xf4/0x15c lib/dump_stack.c:106 dump_stack+0x1c/0x5c lib/dump_stack.c:113 print_circular_bug+0x148/0x1b0 kernel/locking/lockdep.c:2088 check_noncircular+0x290/0x370 kernel/locking/lockdep.c:2215 check_prev_add kernel/locking/lockdep.c:3162 [inline] check_prevs_add kernel/locking/lockdep.c:3281 [inline] validate_chain kernel/locking/lockdep.c:3897 [inline] __lock_acquire+0x3504/0x7280 kernel/locking/lockdep.c:5171 lock_acquire+0x210/0x63c kernel/locking/lockdep.c:5790 __mutex_lock_common+0x1a0/0x1f3c kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799 process_measurement+0x3a8/0x17fc security/integrity/ima/ima_main.c:261 ima_file_check+0xcc/0x118 security/integrity/ima/ima_main.c:534 do_open fs/namei.c:3679 [inline] path_openat+0x2050/0x27a0 fs/namei.c:3834 do_filp_open+0x198/0x38c fs/namei.c:3861 file_open_name fs/open.c:1265 [inline] filp_open+0x160/0x1cc fs/open.c:1285 nvmet_file_ns_enable+0x88/0x2f8 drivers/nvme/target/io-cmd-file.c:41 nvmet_ns_enable+0xe4/0x724 drivers/nvme/target/core.c:576 nvmet_ns_enable_store+0xd4/0x170 drivers/nvme/target/configfs.c:548 flush_write_buffer fs/configfs/file.c:207 [inline] configfs_write_iter+0x260/0x338 fs/configfs/file.c:229 call_write_iter include/linux/fs.h:2271 [inline] new_sync_write fs/read_write.c:491 [inline] vfs_write+0x3c8/0x7c8 fs/read_write.c:584 ksys_write+0x12c/0x228 fs/read_write.c:637 __do_sys_write fs/read_write.c:649 [inline] __se_sys_write fs/read_write.c:646 [inline] __arm64_sys_write+0x7c/0x90 fs/read_write.c:646 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x290 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x13c/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x5c/0x134 arch/arm64/kernel/syscall.c:204 el0_svc+0x58/0x12c arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585 nvmet: transport type 0 not supported