possible deadlock in tcm_alloc

Status: upstream: reported on 2026/08/04 21:00
Reported-by: syzbot+71529afa64b23e366568@syzkaller.appspotmail.com
First crash: 1d02h, last: 21h46m
Similar bugs (3)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.6 possible deadlock in tcm_alloc 4 14 21h18m 1d02h 0/2 upstream: reported on 2026/08/04 20:57
upstream possible deadlock in tcm_alloc prio:low usb 4 syz, C 145 7h09m 2d12h 0/29 upstream: reported C repro on 2026/08/03 10:48
linux-5.15 possible deadlock in tcm_alloc 4 14 21h35m 1d04h 0/3 upstream: reported on 2026/08/04 18:59

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.2.3/4358 is trying to acquire lock:
ffffffff8d8089e8 (tpg_instances_lock){+.+.}-{3:3}, at: tcm_alloc+0x1d/0x1e0 drivers/usb/gadget/function/f_tcm.c:2278

but task is already holding lock:
ffff88807742a310 (&gi->lock){+.+.}-{3:3}, at: config_usb_cfg_link+0x55/0x250 drivers/usb/gadget/configfs.c:429

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #3 (&gi->lock){+.+.}-{3:3}:
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x12d/0xae0 kernel/locking/mutex.c:747
       config_usb_cfg_link+0x55/0x250 drivers/usb/gadget/configfs.c:429
       configfs_symlink+0x5a4/0x13c0 fs/configfs/symlink.c:202
       vfs_symlink+0x245/0x3d0 fs/namei.c:4479
       do_symlinkat+0x1b6/0x400 fs/namei.c:4508
       __do_sys_symlinkat fs/namei.c:4525 [inline]
       __se_sys_symlinkat fs/namei.c:4522 [inline]
       __x64_sys_symlinkat+0x95/0xa0 fs/namei.c:4522
       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

-> #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_mkdirat fs/namei.c:4154 [inline]
       __se_sys_mkdirat fs/namei.c:4152 [inline]
       __x64_sys_mkdirat+0x85/0x90 fs/namei.c:4152
       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
       usbg_make_tpg+0x144/0x580 drivers/usb/gadget/function/f_tcm.c:1357
       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_mkdirat fs/namei.c:4154 [inline]
       __se_sys_mkdirat fs/namei.c:4152 [inline]
       __x64_sys_mkdirat+0x85/0x90 fs/namei.c:4152
       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 (tpg_instances_lock){+.+.}-{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
       tcm_alloc+0x1d/0x1e0 drivers/usb/gadget/function/f_tcm.c:2278
       usb_get_function+0x59/0xa0 drivers/usb/gadget/functions.c:61
       config_usb_cfg_link+0x144/0x250 drivers/usb/gadget/configfs.c:459
       configfs_symlink+0x5a4/0x13c0 fs/configfs/symlink.c:202
       vfs_symlink+0x245/0x3d0 fs/namei.c:4479
       do_symlinkat+0x1b6/0x400 fs/namei.c:4508
       __do_sys_symlinkat fs/namei.c:4525 [inline]
       __se_sys_symlinkat fs/namei.c:4522 [inline]
       __x64_sys_symlinkat+0x95/0xa0 fs/namei.c:4522
       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:
  tpg_instances_lock --> &sb->s_type->i_mutex_key#21 --> &gi->lock

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&gi->lock);
                               lock(&sb->s_type->i_mutex_key#21);
                               lock(&gi->lock);
  lock(tpg_instances_lock);

 *** DEADLOCK ***

3 locks held by syz.2.3/4358:
 #0: ffff88801b700460 (sb_writers#13){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:402
 #1: ffff8880726d5590 (&sb->s_type->i_mutex_key#21){++++}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
 #1: ffff8880726d5590 (&sb->s_type->i_mutex_key#21){++++}-{3:3}, at: configfs_symlink+0x47b/0x13c0 fs/configfs/symlink.c:192
 #2: ffff88807742a310 (&gi->lock){+.+.}-{3:3}, at: config_usb_cfg_link+0x55/0x250 drivers/usb/gadget/configfs.c:429

stack backtrace:
CPU: 0 PID: 4358 Comm: syz.2.3 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
 tcm_alloc+0x1d/0x1e0 drivers/usb/gadget/function/f_tcm.c:2278
 usb_get_function+0x59/0xa0 drivers/usb/gadget/functions.c:61
 config_usb_cfg_link+0x144/0x250 drivers/usb/gadget/configfs.c:459
 configfs_symlink+0x5a4/0x13c0 fs/configfs/symlink.c:202
 vfs_symlink+0x245/0x3d0 fs/namei.c:4479
 do_symlinkat+0x1b6/0x400 fs/namei.c:4508
 __do_sys_symlinkat fs/namei.c:4525 [inline]
 __se_sys_symlinkat fs/namei.c:4522 [inline]
 __x64_sys_symlinkat+0x95/0xa0 fs/namei.c:4522
 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:0x7fce3f59e019
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:00007fce40475028 EFLAGS: 00000246 ORIG_RAX: 000000000000010a
RAX: ffffffffffffffda RBX: 00007fce3f825fa0 RCX: 00007fce3f59e019
RDX: 0000200000000a40 RSI: ffffffffffffff9c RDI: 0000200000000a00
RBP: 00007fce3f63500c R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fce3f826038 R14: 00007fce3f825fa0 R15: 00007ffd8c3948c8
 </TASK>

Crashes (24):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/08/05 01:56 linux-6.1.y fb28aa725e05 d4abbeac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in tcm_alloc
2026/08/05 01:54 linux-6.1.y fb28aa725e05 d4abbeac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in tcm_alloc
2026/08/05 01:46 linux-6.1.y fb28aa725e05 d4abbeac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in tcm_alloc
2026/08/05 01:46 linux-6.1.y fb28aa725e05 d4abbeac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in tcm_alloc
2026/08/05 01:11 linux-6.1.y fb28aa725e05 d4abbeac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in tcm_alloc
2026/08/05 01:10 linux-6.1.y fb28aa725e05 d4abbeac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in tcm_alloc
2026/08/05 00:36 linux-6.1.y fb28aa725e05 d4abbeac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in tcm_alloc
2026/08/05 00:34 linux-6.1.y fb28aa725e05 d4abbeac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in tcm_alloc
2026/08/04 23:31 linux-6.1.y fb28aa725e05 d4abbeac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in tcm_alloc
2026/08/04 23:31 linux-6.1.y fb28aa725e05 d4abbeac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in tcm_alloc
2026/08/04 22:43 linux-6.1.y fb28aa725e05 d4abbeac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in tcm_alloc
2026/08/04 22:43 linux-6.1.y fb28aa725e05 d4abbeac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in tcm_alloc
2026/08/04 22:03 linux-6.1.y fb28aa725e05 d4abbeac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in tcm_alloc
2026/08/04 22:02 linux-6.1.y fb28aa725e05 d4abbeac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in tcm_alloc
2026/08/04 21:29 linux-6.1.y fb28aa725e05 d4abbeac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in tcm_alloc
2026/08/04 21:29 linux-6.1.y fb28aa725e05 d4abbeac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in tcm_alloc
2026/08/04 21:28 linux-6.1.y fb28aa725e05 d4abbeac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in tcm_alloc
2026/08/04 21:23 linux-6.1.y fb28aa725e05 d4abbeac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in tcm_alloc
2026/08/04 21:23 linux-6.1.y fb28aa725e05 d4abbeac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in tcm_alloc
2026/08/04 21:21 linux-6.1.y fb28aa725e05 d4abbeac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in tcm_alloc
2026/08/04 21:01 linux-6.1.y fb28aa725e05 d4abbeac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in tcm_alloc
2026/08/04 21:01 linux-6.1.y fb28aa725e05 d4abbeac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in tcm_alloc
2026/08/04 20:59 linux-6.1.y fb28aa725e05 d4abbeac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in tcm_alloc
2026/08/04 20:59 linux-6.1.y fb28aa725e05 d4abbeac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in tcm_alloc
* Struck through repros no longer work on HEAD.