nvmet: adding nsid 1 to subsystem testsubsys ====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Tainted: G L ------------------------------------------------------ syz.6.508/7310 is trying to acquire lock: ffff0000d4afc460 (sb_writers#5){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:494 but task is already holding lock: ffff0000f109a868 (&subsys->lock#2){+.+.}-{4:4}, at: nvmet_ns_enable+0x58/0x508 drivers/nvme/target/core.c:583 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #3 (&subsys->lock#2){+.+.}-{4:4}: __mutex_lock_common kernel/locking/mutex.c:646 [inline] __mutex_lock+0x164/0x1078 kernel/locking/mutex.c:821 mutex_lock_nested+0x24/0x30 kernel/locking/mutex.c:874 nvmet_ns_device_path_store+0x5c/0x14c drivers/nvme/target/configfs.c:538 flush_write_buffer fs/configfs/file.c:207 [inline] configfs_write_iter+0x27c/0x354 fs/configfs/file.c:229 new_sync_write fs/read_write.c:595 [inline] vfs_write+0x51c/0xa0c fs/read_write.c:687 ksys_write+0x12c/0x228 fs/read_write.c:739 __do_sys_write fs/read_write.c:750 [inline] __se_sys_write fs/read_write.c:747 [inline] __arm64_sys_write+0x84/0x98 fs/read_write.c:747 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x244 arch/arm64/kernel/syscall.c:49 el0_svc_common+0xec/0x23c arch/arm64/kernel/syscall.c:121 do_el0_svc+0x4c/0x5c arch/arm64/kernel/syscall.c:140 el0_svc+0x60/0x1d8 arch/arm64/kernel/entry-common.c:796 el0t_64_sync_handler+0x44/0x104 arch/arm64/kernel/entry-common.c:815 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:606 -> #2 (&p->frag_sem){.+.+}-{4:4}: down_read+0x58/0x2bc kernel/locking/rwsem.c:1574 __configfs_open_file+0xd4/0x688 fs/configfs/file.c:304 configfs_open_file+0x2c/0x3c fs/configfs/file.c:392 do_dentry_open+0x5c4/0xfbc fs/open.c:996 vfs_open+0x44/0x2dc fs/open.c:1101 dentry_open+0x74/0xc0 fs/open.c:1124 ima_calc_file_hash+0x120/0x5cc security/integrity/ima/ima_crypto.c:269 ima_collect_measurement+0x420/0x874 security/integrity/ima/ima_api.c:300 process_measurement+0xe64/0x17d4 security/integrity/ima/ima_main.c:425 ima_file_check+0xd0/0x11c security/integrity/ima/ima_main.c:685 security_file_post_open+0x94/0x280 security/security.c:2755 do_open fs/namei.c:4839 [inline] path_openat+0x10d0/0x18f0 fs/namei.c:5000 do_file_open+0x1c8/0x2e8 fs/namei.c:5029 do_sys_openat2+0x114/0x1e8 fs/open.c:1417 do_sys_open+0xb0/0xe0 fs/open.c:1423 __do_sys_openat fs/open.c:1439 [inline] __se_sys_openat fs/open.c:1434 [inline] __arm64_sys_openat+0xa8/0xc4 fs/open.c:1434 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x244 arch/arm64/kernel/syscall.c:49 el0_svc_common+0xec/0x23c arch/arm64/kernel/syscall.c:121 do_el0_svc+0x4c/0x5c arch/arm64/kernel/syscall.c:140 el0_svc+0x60/0x1d8 arch/arm64/kernel/entry-common.c:796 el0t_64_sync_handler+0x44/0x104 arch/arm64/kernel/entry-common.c:815 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:606 -> #1 (&ima_iint_mutex_key[depth]){+.+.}-{4:4}: __mutex_lock_common kernel/locking/mutex.c:646 [inline] __mutex_lock+0x164/0x1078 kernel/locking/mutex.c:821 mutex_lock_nested+0x24/0x30 kernel/locking/mutex.c:874 process_measurement+0x5b4/0x17d4 security/integrity/ima/ima_main.c:319 ima_file_check+0xd0/0x11c security/integrity/ima/ima_main.c:685 security_file_post_open+0x94/0x280 security/security.c:2755 do_open fs/namei.c:4839 [inline] path_openat+0x10d0/0x18f0 fs/namei.c:5000 do_file_open+0x1c8/0x2e8 fs/namei.c:5029 do_sys_openat2+0x114/0x1e8 fs/open.c:1417 do_sys_open+0xb0/0xe0 fs/open.c:1423 __do_sys_openat fs/open.c:1439 [inline] __se_sys_openat fs/open.c:1434 [inline] __arm64_sys_openat+0xa8/0xc4 fs/open.c:1434 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x244 arch/arm64/kernel/syscall.c:49 el0_svc_common+0xec/0x23c arch/arm64/kernel/syscall.c:121 do_el0_svc+0x4c/0x5c arch/arm64/kernel/syscall.c:140 el0_svc+0x60/0x1d8 arch/arm64/kernel/entry-common.c:796 el0t_64_sync_handler+0x44/0x104 arch/arm64/kernel/entry-common.c:815 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:606 -> #0 (sb_writers#5){.+.+}-{0:0}: check_prev_add kernel/locking/lockdep.c:3209 [inline] check_prevs_add kernel/locking/lockdep.c:3328 [inline] validate_chain kernel/locking/lockdep.c:3952 [inline] __lock_acquire+0x1660/0x2b08 kernel/locking/lockdep.c:5288 lock_acquire+0x13c/0x320 kernel/locking/lockdep.c:5942 percpu_down_read_internal include/linux/percpu-rwsem.h:53 [inline] percpu_down_read_freezable include/linux/percpu-rwsem.h:83 [inline] __sb_start_write include/linux/fs/super.h:19 [inline] sb_start_write+0x5c/0x208 include/linux/fs/super.h:125 mnt_want_write+0x44/0x9c fs/namespace.c:494 lookup_open+0x174/0x1180 fs/namei.c:4451 open_last_lookups fs/namei.c:4767 [inline] path_openat+0x50c/0x18f0 fs/namei.c:4997 do_file_open+0x1c8/0x2e8 fs/namei.c:5029 file_open_name+0x148/0x1a0 fs/open.c:1375 filp_open+0x3c/0x60 fs/open.c:1392 nvmet_file_ns_enable+0x88/0x30c drivers/nvme/target/io-cmd-file.c:41 nvmet_ns_enable+0xcc/0x508 drivers/nvme/target/core.c:601 nvmet_ns_enable_store+0xd4/0x170 drivers/nvme/target/configfs.c:737 flush_write_buffer fs/configfs/file.c:207 [inline] configfs_write_iter+0x27c/0x354 fs/configfs/file.c:229 new_sync_write fs/read_write.c:595 [inline] vfs_write+0x51c/0xa0c fs/read_write.c:687 ksys_write+0x12c/0x228 fs/read_write.c:739 __do_sys_write fs/read_write.c:750 [inline] __se_sys_write fs/read_write.c:747 [inline] __arm64_sys_write+0x84/0x98 fs/read_write.c:747 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x244 arch/arm64/kernel/syscall.c:49 el0_svc_common+0xec/0x23c arch/arm64/kernel/syscall.c:121 do_el0_svc+0x4c/0x5c arch/arm64/kernel/syscall.c:140 el0_svc+0x60/0x1d8 arch/arm64/kernel/entry-common.c:796 el0t_64_sync_handler+0x44/0x104 arch/arm64/kernel/entry-common.c:815 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:606 other info that might help us debug this: Chain exists of: sb_writers#5 --> &p->frag_sem --> &subsys->lock#2 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&subsys->lock#2); lock(&p->frag_sem); lock(&subsys->lock#2); rlock(sb_writers#5); *** DEADLOCK *** locks held by syz.6.508/7310: 6, last CPU#0: #0: ffff0000f8e495f0 (&f->f_pos_lock){+.+.}-{4:4}, at: fdget_pos+0x100/0x144 fs/file.c:1259 #1: ffff0000c39b2460 (sb_writers#22){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:2753 [inline] #1: ffff0000c39b2460 (sb_writers#22){.+.+}-{0:0}, at: vfs_write+0x248/0xa0c fs/read_write.c:683 #2: ffff0000c1912080 (&buffer->mutex){+.+.}-{4:4}, at: configfs_write_iter+0x74/0x354 fs/configfs/file.c:226 #3: ffff0000cf400370 (&p->frag_sem){.+.+}-{4:4}, at: flush_write_buffer fs/configfs/file.c:205 [inline] #3: ffff0000cf400370 (&p->frag_sem){.+.+}-{4:4}, at: configfs_write_iter+0x1c4/0x354 fs/configfs/file.c:229 #4: ffff80008937dfe8 (nvmet_config_sem){+.+.}-{4:4}, at: nvmet_ns_enable_store+0xc4/0x170 drivers/nvme/target/configfs.c:735 #5: ffff0000f109a868 (&subsys->lock#2){+.+.}-{4:4}, at: nvmet_ns_enable+0x58/0x508 drivers/nvme/target/core.c:583 stack backtrace: CPU: 0 UID: 0 PID: 7310 Comm: syz.6.508 Tainted: G L syzkaller #0 PREEMPT Tainted: [L]=SOFTLOCKUP Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/14/2026 Call trace: show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:499 (C) __dump_stack+0x30/0x40 lib/dump_stack.c:94 dump_stack_lvl+0xd8/0x12c lib/dump_stack.c:120 dump_stack+0x1c/0x28 lib/dump_stack.c:129 print_circular_bug+0x328/0x330 kernel/locking/lockdep.c:2087 check_noncircular+0x158/0x174 kernel/locking/lockdep.c:2219 check_prev_add kernel/locking/lockdep.c:3209 [inline] check_prevs_add kernel/locking/lockdep.c:3328 [inline] validate_chain kernel/locking/lockdep.c:3952 [inline] __lock_acquire+0x1660/0x2b08 kernel/locking/lockdep.c:5288 lock_acquire+0x13c/0x320 kernel/locking/lockdep.c:5942 percpu_down_read_internal include/linux/percpu-rwsem.h:53 [inline] percpu_down_read_freezable include/linux/percpu-rwsem.h:83 [inline] __sb_start_write include/linux/fs/super.h:19 [inline] sb_start_write+0x5c/0x208 include/linux/fs/super.h:125 mnt_want_write+0x44/0x9c fs/namespace.c:494 lookup_open+0x174/0x1180 fs/namei.c:4451 open_last_lookups fs/namei.c:4767 [inline] path_openat+0x50c/0x18f0 fs/namei.c:4997 do_file_open+0x1c8/0x2e8 fs/namei.c:5029 file_open_name+0x148/0x1a0 fs/open.c:1375 filp_open+0x3c/0x60 fs/open.c:1392 nvmet_file_ns_enable+0x88/0x30c drivers/nvme/target/io-cmd-file.c:41 nvmet_ns_enable+0xcc/0x508 drivers/nvme/target/core.c:601 nvmet_ns_enable_store+0xd4/0x170 drivers/nvme/target/configfs.c:737 flush_write_buffer fs/configfs/file.c:207 [inline] configfs_write_iter+0x27c/0x354 fs/configfs/file.c:229 new_sync_write fs/read_write.c:595 [inline] vfs_write+0x51c/0xa0c fs/read_write.c:687 ksys_write+0x12c/0x228 fs/read_write.c:739 __do_sys_write fs/read_write.c:750 [inline] __se_sys_write fs/read_write.c:747 [inline] __arm64_sys_write+0x84/0x98 fs/read_write.c:747 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x244 arch/arm64/kernel/syscall.c:49 el0_svc_common+0xec/0x23c arch/arm64/kernel/syscall.c:121 do_el0_svc+0x4c/0x5c arch/arm64/kernel/syscall.c:140 el0_svc+0x60/0x1d8 arch/arm64/kernel/entry-common.c:796 el0t_64_sync_handler+0x44/0x104 arch/arm64/kernel/entry-common.c:815 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:606 nvmet: failed to open file ./img: (-2)