====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.6.360/5794 is trying to acquire lock: ffffffff8cc24690 (&subsys->su_mutex){+.+.}-{3:3}, at: configfs_rmdir+0x638/0x980 fs/configfs/dir.c:1552 but task is already holding lock: ffff888070a1d080 (&sb->s_type->i_mutex_key#26){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:793 [inline] ffff888070a1d080 (&sb->s_type->i_mutex_key#26){+.+.}-{3:3}, at: vfs_rmdir+0xe1/0x410 fs/namei.c:4190 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&sb->s_type->i_mutex_key#26){+.+.}-{3:3}: down_write+0x38/0x60 kernel/locking/rwsem.c:1551 inode_lock include/linux/fs.h:793 [inline] configfs_depend_item_unlocked+0x14c/0x450 fs/configfs/dir.c:1251 usbg_make_tpg+0x1dd/0x550 drivers/usb/gadget/function/f_tcm.c:1357 target_fabric_make_tpg+0xa0/0x6d0 drivers/target/target_core_fabric_configfs.c:845 configfs_mkdir+0x511/0x9e0 fs/configfs/dir.c:1356 vfs_mkdir+0x386/0x570 fs/namei.c:4116 do_mkdirat+0x1dd/0x5c0 fs/namei.c:4141 __do_sys_mkdirat fs/namei.c:4156 [inline] __se_sys_mkdirat fs/namei.c:4154 [inline] __x64_sys_mkdirat+0x85/0x90 fs/namei.c:4154 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 -> #1 (tpg_instances_lock){+.+.}-{3:3}: __mutex_lock_common+0x1e5/0x2400 kernel/locking/mutex.c:596 __mutex_lock kernel/locking/mutex.c:729 [inline] mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743 usbg_make_tpg+0xf5/0x550 drivers/usb/gadget/function/f_tcm.c:1334 target_fabric_make_tpg+0xa0/0x6d0 drivers/target/target_core_fabric_configfs.c:845 configfs_mkdir+0x511/0x9e0 fs/configfs/dir.c:1356 vfs_mkdir+0x386/0x570 fs/namei.c:4116 do_mkdirat+0x1dd/0x5c0 fs/namei.c:4141 __do_sys_mkdirat fs/namei.c:4156 [inline] __se_sys_mkdirat fs/namei.c:4154 [inline] __x64_sys_mkdirat+0x85/0x90 fs/namei.c:4154 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 -> #0 (&subsys->su_mutex){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3120 [inline] check_prevs_add kernel/locking/lockdep.c:3239 [inline] validate_chain kernel/locking/lockdep.c:3855 [inline] __lock_acquire+0x38f7/0x7d40 kernel/locking/lockdep.c:5120 lock_acquire+0x19f/0x400 kernel/locking/lockdep.c:5737 __mutex_lock_common+0x1e5/0x2400 kernel/locking/mutex.c:596 __mutex_lock kernel/locking/mutex.c:729 [inline] mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743 configfs_rmdir+0x638/0x980 fs/configfs/dir.c:1552 vfs_rmdir+0x19d/0x410 fs/namei.c:4200 do_rmdir+0x27f/0x710 fs/namei.c:4261 __do_sys_unlinkat fs/namei.c:4441 [inline] __se_sys_unlinkat fs/namei.c:4435 [inline] __x64_sys_unlinkat+0xc0/0xe0 fs/namei.c:4435 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 other info that might help us debug this: Chain exists of: &subsys->su_mutex --> tpg_instances_lock --> &sb->s_type->i_mutex_key#26 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&sb->s_type->i_mutex_key#26); lock(tpg_instances_lock); lock(&sb->s_type->i_mutex_key#26); lock(&subsys->su_mutex); *** DEADLOCK *** 3 locks held by syz.6.360/5794: #0: ffff88801e09e460 (sb_writers#18){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:386 #1: ffff888070a35aa0 (&sb->s_type->i_mutex_key#7/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:828 [inline] #1: ffff888070a35aa0 (&sb->s_type->i_mutex_key#7/1){+.+.}-{3:3}, at: do_rmdir+0x1b0/0x710 fs/namei.c:4248 #2: ffff888070a1d080 (&sb->s_type->i_mutex_key#26){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:793 [inline] #2: ffff888070a1d080 (&sb->s_type->i_mutex_key#26){+.+.}-{3:3}, at: vfs_rmdir+0xe1/0x410 fs/namei.c:4190 stack backtrace: CPU: 0 PID: 5794 Comm: syz.6.360 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026 Call Trace: dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106 check_noncircular+0x2f8/0x400 kernel/locking/lockdep.c:2178 check_prev_add kernel/locking/lockdep.c:3120 [inline] check_prevs_add kernel/locking/lockdep.c:3239 [inline] validate_chain kernel/locking/lockdep.c:3855 [inline] __lock_acquire+0x38f7/0x7d40 kernel/locking/lockdep.c:5120 lock_acquire+0x19f/0x400 kernel/locking/lockdep.c:5737 __mutex_lock_common+0x1e5/0x2400 kernel/locking/mutex.c:596 __mutex_lock kernel/locking/mutex.c:729 [inline] mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743 configfs_rmdir+0x638/0x980 fs/configfs/dir.c:1552 vfs_rmdir+0x19d/0x410 fs/namei.c:4200 do_rmdir+0x27f/0x710 fs/namei.c:4261 __do_sys_unlinkat fs/namei.c:4441 [inline] __se_sys_unlinkat fs/namei.c:4435 [inline] __x64_sys_unlinkat+0xc0/0xe0 fs/namei.c:4435 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 RIP: 0033:0x7efd509a5159 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:00007efd4ebfd028 EFLAGS: 00000246 ORIG_RAX: 0000000000000107 RAX: ffffffffffffffda RBX: 00007efd50c2cfa0 RCX: 00007efd509a5159 RDX: 0000000000000200 RSI: 00002000000002c0 RDI: ffffffffffffff9c RBP: 00007efd50a3c06b R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007efd50c2d038 R14: 00007efd50c2cfa0 R15: 00007ffc3a764fd8