======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.0.18/4426 is trying to acquire lock:
ffffffff8d7b2f90 (gadget_subsys.su_mutex){+.+.}-{3:3}, at: configfs_rmdir+0x638/0x980 fs/configfs/dir.c:1556

but task is already holding lock:
ffff88805a945590 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
ffff88805a945590 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: vfs_rmdir+0xea/0x4a0 fs/namei.c:4188

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}:
       down_write+0x36/0x60 kernel/locking/rwsem.c:1573
       inode_lock include/linux/fs.h:758 [inline]
       configfs_depend_item_unlocked+0x14f/0x430 fs/configfs/dir.c:1255
       usbg_make_tpg+0x1f3/0x580 drivers/usb/gadget/function/f_tcm.c:1365
       target_fabric_make_tpg+0xa0/0x6d0 drivers/target/target_core_fabric_configfs.c:905
       configfs_mkdir+0x511/0x9e0 fs/configfs/dir.c:1360
       vfs_mkdir+0x386/0x570 fs/namei.c:4114
       do_mkdirat+0x1d8/0x440 fs/namei.c:4139
       __do_sys_mkdir fs/namei.c:4159 [inline]
       __se_sys_mkdir fs/namei.c:4157 [inline]
       __x64_sys_mkdir+0x6a/0x80 fs/namei.c:4157
       do_syscall_x64 arch/x86/entry/common.c:46 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #1 (&opts->dep_lock){+.+.}-{3:3}:
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x12d/0xae0 kernel/locking/mutex.c:747
       tcm_set_name+0x26/0x90 drivers/usb/gadget/function/f_tcm.c:2219
       function_make+0x195/0x350 drivers/usb/gadget/configfs.c:625
       configfs_mkdir+0x511/0x9e0 fs/configfs/dir.c:1360
       vfs_mkdir+0x386/0x570 fs/namei.c:4114
       do_mkdirat+0x1d8/0x440 fs/namei.c:4139
       __do_sys_mkdir fs/namei.c:4159 [inline]
       __se_sys_mkdir fs/namei.c:4157 [inline]
       __x64_sys_mkdir+0x6a/0x80 fs/namei.c:4157
       do_syscall_x64 arch/x86/entry/common.c:46 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #0 (gadget_subsys.su_mutex){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3095 [inline]
       check_prevs_add kernel/locking/lockdep.c:3214 [inline]
       validate_chain kernel/locking/lockdep.c:3830 [inline]
       __lock_acquire+0x2d18/0x7c40 kernel/locking/lockdep.c:5063
       lock_acquire+0x1bb/0x4a0 kernel/locking/lockdep.c:5676
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x12d/0xae0 kernel/locking/mutex.c:747
       configfs_rmdir+0x638/0x980 fs/configfs/dir.c:1556
       vfs_rmdir+0x34e/0x4a0 fs/namei.c:4199
       do_rmdir+0x29a/0x5c0 fs/namei.c:4260
       __do_sys_rmdir fs/namei.c:4279 [inline]
       __se_sys_rmdir fs/namei.c:4277 [inline]
       __x64_sys_rmdir+0x45/0x50 fs/namei.c:4277
       do_syscall_x64 arch/x86/entry/common.c:46 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

other info that might help us debug this:

Chain exists of:
  gadget_subsys.su_mutex --> &opts->dep_lock --> &sb->s_type->i_mutex_key#21

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&sb->s_type->i_mutex_key#21);
                               lock(&opts->dep_lock);
                               lock(&sb->s_type->i_mutex_key#21);
  lock(gadget_subsys.su_mutex);

 *** DEADLOCK ***

3 locks held by syz.0.18/4426:
 #0: ffff888144aa8460 (sb_writers#13){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:402
 #1: ffff88805a93b900 (&default_group_class[depth - 1]#2/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:793 [inline]
 #1: ffff88805a93b900 (&default_group_class[depth - 1]#2/1){+.+.}-{3:3}, at: do_rmdir+0x1b7/0x5c0 fs/namei.c:4247
 #2: ffff88805a945590 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
 #2: ffff88805a945590 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: vfs_rmdir+0xea/0x4a0 fs/namei.c:4188

stack backtrace:
CPU: 1 PID: 4426 Comm: syz.0.18 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0x188/0x24e lib/dump_stack.c:106
 check_noncircular+0x296/0x330 kernel/locking/lockdep.c:2170
 check_prev_add kernel/locking/lockdep.c:3095 [inline]
 check_prevs_add kernel/locking/lockdep.c:3214 [inline]
 validate_chain kernel/locking/lockdep.c:3830 [inline]
 __lock_acquire+0x2d18/0x7c40 kernel/locking/lockdep.c:5063
 lock_acquire+0x1bb/0x4a0 kernel/locking/lockdep.c:5676
 __mutex_lock_common kernel/locking/mutex.c:603 [inline]
 __mutex_lock+0x12d/0xae0 kernel/locking/mutex.c:747
 configfs_rmdir+0x638/0x980 fs/configfs/dir.c:1556
 vfs_rmdir+0x34e/0x4a0 fs/namei.c:4199
 do_rmdir+0x29a/0x5c0 fs/namei.c:4260
 __do_sys_rmdir fs/namei.c:4279 [inline]
 __se_sys_rmdir fs/namei.c:4277 [inline]
 __x64_sys_rmdir+0x45/0x50 fs/namei.c:4277
 do_syscall_x64 arch/x86/entry/common.c:46 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f299db9e019
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:00007ffc81fba108 EFLAGS: 00000246 ORIG_RAX: 0000000000000054
RAX: ffffffffffffffda RBX: 00007f299de25fa0 RCX: 00007f299db9e019
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000200000000000
RBP: 00007f299dc3500c R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f299de25fac R14: 00007f299de25fa0 R15: 00007f299de25fa0
 </TASK>
printk: console [ttyGS0] disabled