====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Tainted: G L ------------------------------------------------------ syz.7.2246/16255 is trying to acquire lock: ffffffff8f6d85c0 (nvmf_dev_mutex){+.+.}-{4:4}, at: nvmf_dev_show+0x2c/0x180 drivers/nvme/host/fabrics.c:1444 but task is already holding lock: ffff8880461c3878 (&p->lock){+.+.}-{4:4}, at: seq_read_iter+0xa4/0xca0 fs/seq_file.c:183 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #4 (&p->lock){+.+.}-{4:4}: __mutex_lock_common kernel/locking/mutex.c:646 [inline] __mutex_lock+0x19d/0x1550 kernel/locking/mutex.c:821 seq_read_iter+0xa4/0xca0 fs/seq_file.c:183 __kernel_read+0x4ca/0x960 fs/read_write.c:532 integrity_kernel_read+0x89/0xd0 security/integrity/iint.c:28 ima_calc_file_hash_tfm security/integrity/ima/ima_crypto.c:222 [inline] ima_calc_file_hash+0x451/0x890 security/integrity/ima/ima_crypto.c:280 ima_collect_measurement+0x51b/0xa00 security/integrity/ima/ima_api.c:300 process_measurement+0x1272/0x1c10 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:4839 [inline] path_openat+0x1485/0x1d60 fs/namei.c:5000 do_file_open+0x23e/0x4a0 fs/namei.c:5029 do_sys_openat2+0x115/0x200 fs/open.c:1417 do_sys_open fs/open.c:1423 [inline] __do_sys_openat fs/open.c:1439 [inline] __se_sys_openat fs/open.c:1434 [inline] __x64_sys_openat+0x138/0x170 fs/open.c:1434 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline] do_syscall_64+0x166/0x510 arch/x86/entry/syscall_64.c:84 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #3 (&ima_iint_mutex_key[depth]){+.+.}-{4:4}: __mutex_lock_common kernel/locking/mutex.c:646 [inline] __mutex_lock+0x19d/0x1550 kernel/locking/mutex.c:821 process_measurement+0x7d0/0x1c10 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:4839 [inline] path_openat+0x1485/0x1d60 fs/namei.c:5000 do_file_open+0x23e/0x4a0 fs/namei.c:5029 file_open_name fs/open.c:1375 [inline] filp_open+0x16d/0x1d0 fs/open.c:1392 kernel_read_file_from_path_initns+0xde/0x1e0 fs/kernel_read_file.c:159 fw_get_filesystem_firmware drivers/base/firmware_loader/main.c:549 [inline] _request_firmware+0xa50/0x1780 drivers/base/firmware_loader/main.c:873 request_firmware+0x36/0x50 drivers/base/firmware_loader/main.c:948 reg_reload_regdb+0x95/0x490 net/wireless/reg.c:1067 genl_family_rcv_msg_doit+0x233/0x340 net/netlink/genetlink.c:1114 genl_family_rcv_msg net/netlink/genetlink.c:1194 [inline] genl_rcv_msg+0x614/0x7a0 net/netlink/genetlink.c:1209 netlink_rcv_skb+0x226/0x4a0 net/netlink/af_netlink.c:2556 genl_rcv+0x28/0x40 net/netlink/genetlink.c:1218 netlink_unicast_kernel net/netlink/af_netlink.c:1319 [inline] netlink_unicast+0x7bb/0x940 net/netlink/af_netlink.c:1345 netlink_sendmsg+0x813/0xb40 net/netlink/af_netlink.c:1900 sock_sendmsg_nosec+0x13a/0x180 net/socket.c:800 __sock_sendmsg net/socket.c:815 [inline] ____sys_sendmsg+0x54e/0x850 net/socket.c:2709 ___sys_sendmsg+0x2a5/0x360 net/socket.c:2763 __sys_sendmsg net/socket.c:2795 [inline] __do_sys_sendmsg net/socket.c:2800 [inline] __se_sys_sendmsg net/socket.c:2798 [inline] __x64_sys_sendmsg+0x1b1/0x290 net/socket.c:2798 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline] do_syscall_64+0x166/0x510 arch/x86/entry/syscall_64.c:84 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #2 (cb_lock){++++}-{4:4}: down_read+0x4a/0x330 kernel/locking/rwsem.c:1574 genl_release+0x89/0x1e0 net/netlink/genetlink.c:697 netlink_release+0xe91/0x1a80 net/netlink/af_netlink.c:735 __sock_release+0xa0/0x1f0 net/socket.c:735 sock_close+0x1c/0x30 net/socket.c:1526 __fput+0x418/0xa50 fs/file_table.c:512 fput_close_sync+0x11f/0x240 fs/file_table.c:617 __do_sys_close fs/open.c:1560 [inline] __se_sys_close fs/open.c:1545 [inline] __x64_sys_close+0x7e/0x110 fs/open.c:1545 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline] do_syscall_64+0x166/0x510 arch/x86/entry/syscall_64.c:84 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #1 (&sb->s_type->i_mutex_key#13){+.+.}-{4:4}: down_write+0x96/0x200 kernel/locking/rwsem.c:1631 inode_lock include/linux/fs.h:1025 [inline] __sock_release+0x7a/0x1f0 net/socket.c:734 sock_close+0x1c/0x30 net/socket.c:1526 __fput+0x418/0xa50 fs/file_table.c:512 nvme_tcp_alloc_queue+0x1837/0x1eb0 drivers/nvme/host/tcp.c:1922 nvme_tcp_alloc_admin_queue drivers/nvme/host/tcp.c:2107 [inline] nvme_tcp_configure_admin_queue+0x1f/0x400 drivers/nvme/host/tcp.c:2261 nvme_tcp_setup_ctrl+0xba/0x1880 drivers/nvme/host/tcp.c:2391 nvme_tcp_create_ctrl+0x811/0xc10 drivers/nvme/host/tcp.c:3014 nvmf_create_ctrl drivers/nvme/host/fabrics.c:1359 [inline] nvmf_dev_write+0x24ca/0x2d90 drivers/nvme/host/fabrics.c:1406 vfs_write+0x296/0xba0 fs/read_write.c:685 ksys_write+0x150/0x270 fs/read_write.c:739 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline] do_syscall_64+0x166/0x510 arch/x86/entry/syscall_64.c:84 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (nvmf_dev_mutex){+.+.}-{4:4}: check_prev_add kernel/locking/lockdep.c:3181 [inline] check_prevs_add kernel/locking/lockdep.c:3300 [inline] validate_chain kernel/locking/lockdep.c:3924 [inline] __lock_acquire+0x15ff/0x2e50 kernel/locking/lockdep.c:5254 lock_acquire+0x115/0x350 kernel/locking/lockdep.c:5908 __mutex_lock_common kernel/locking/mutex.c:646 [inline] __mutex_lock+0x19d/0x1550 kernel/locking/mutex.c:821 nvmf_dev_show+0x2c/0x180 drivers/nvme/host/fabrics.c:1444 seq_read_iter+0x463/0xca0 fs/seq_file.c:231 seq_read+0x367/0x480 fs/seq_file.c:163 vfs_read+0x213/0xa80 fs/read_write.c:572 ksys_read+0x150/0x270 fs/read_write.c:716 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline] do_syscall_64+0x166/0x510 arch/x86/entry/syscall_64.c:84 entry_SYSCALL_64_after_hwframe+0x77/0x7f other info that might help us debug this: Chain exists of: nvmf_dev_mutex --> &ima_iint_mutex_key[depth] --> &p->lock Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&p->lock); lock(&ima_iint_mutex_key[depth]); lock(&p->lock); lock(nvmf_dev_mutex); *** DEADLOCK *** locks held by syz.7.2246/16255: 1, last CPU#0: #0: ffff8880461c3878 (&p->lock){+.+.}-{4:4}, at: seq_read_iter+0xa4/0xca0 fs/seq_file.c:183 stack backtrace: CPU: 0 UID: 0 PID: 16255 Comm: syz.7.2246 Tainted: G L syzkaller #0 PREEMPT(full) Tainted: [L]=SOFTLOCKUP Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026 Call Trace: dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120 print_circular_bug+0x2e2/0x300 kernel/locking/lockdep.c:2059 check_noncircular+0x12f/0x150 kernel/locking/lockdep.c:2191 check_prev_add kernel/locking/lockdep.c:3181 [inline] check_prevs_add kernel/locking/lockdep.c:3300 [inline] validate_chain kernel/locking/lockdep.c:3924 [inline] __lock_acquire+0x15ff/0x2e50 kernel/locking/lockdep.c:5254 lock_acquire+0x115/0x350 kernel/locking/lockdep.c:5908 __mutex_lock_common kernel/locking/mutex.c:646 [inline] __mutex_lock+0x19d/0x1550 kernel/locking/mutex.c:821 nvmf_dev_show+0x2c/0x180 drivers/nvme/host/fabrics.c:1444 seq_read_iter+0x463/0xca0 fs/seq_file.c:231 seq_read+0x367/0x480 fs/seq_file.c:163 vfs_read+0x213/0xa80 fs/read_write.c:572 ksys_read+0x150/0x270 fs/read_write.c:716 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline] do_syscall_64+0x166/0x510 arch/x86/entry/syscall_64.c:84 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fef6d99e0d9 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:00007fef6e8b2028 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 RAX: ffffffffffffffda RBX: 00007fef6dc25fa0 RCX: 00007fef6d99e0d9 RDX: 0000000000000971 RSI: 0000200000002900 RDI: 0000000000000004 RBP: 00007fef6da35024 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fef6dc26038 R14: 00007fef6dc25fa0 R15: 00007fff0460b4a8