[v5.15] possible deadlock in uvcg_frame_dw_frame_interval_store

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: aabd761612db Linux 5.15.215
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10390679580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f161cbc9aef65db0
dashboard link: https://syzkaller.appspot.com/bug?extid=9e7b9ab5531353749852
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f636f56d3662/disk-aabd7616.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f1a46620f40c/vmlinux-aabd7616.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9b78bb48b022/bzImage-aabd7616.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+9e7b9a...@syzkaller.appspotmail.com

======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.3.1017/8654 is trying to acquire lock:
ffffffff8ceceff0 (gadget_subsys.su_mutex){+.+.}-{3:3}, at: uvcg_frame_dw_frame_interval_store+0xde/0x9c0 drivers/usb/gadget/function/uvc_configfs.c:1336

but task is already holding lock:
ffff888025481678 (&p->frag_sem){++++}-{3:3}, at: flush_write_buffer fs/configfs/file.c:205 [inline]
ffff888025481678 (&p->frag_sem){++++}-{3:3}, at: configfs_write_iter+0x20e/0x400 fs/configfs/file.c:229

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #3 (&p->frag_sem){++++}-{3:3}:
down_write_killable+0x46/0x90 kernel/locking/rwsem.c:1562
configfs_rmdir+0x3e0/0x980 fs/configfs/dir.c:1534
vfs_rmdir+0x19d/0x410 fs/namei.c:4157
do_rmdir+0x27f/0x710 fs/namei.c:4218
__do_sys_rmdir fs/namei.c:4237 [inline]
__se_sys_rmdir fs/namei.c:4235 [inline]
__x64_sys_rmdir+0x45/0x50 fs/namei.c:4235
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

-> #2 (&sb->s_type->i_mutex_key#21){++++}-{3:3}:
down_write+0x38/0x60 kernel/locking/rwsem.c:1551
inode_lock include/linux/fs.h:787 [inline]
configfs_depend_item_unlocked+0x14f/0x430 fs/configfs/dir.c:1255
usbg_make_tpg+0x1f3/0x580 drivers/usb/gadget/function/f_tcm.c:1351
target_fabric_make_tpg+0xa0/0x6d0 drivers/target/target_core_fabric_configfs.c:837
configfs_mkdir+0x511/0x9e0 fs/configfs/dir.c:1360
vfs_mkdir+0x386/0x570 fs/namei.c:4073
do_mkdirat+0x1dd/0x5c0 fs/namei.c:4098
__do_sys_mkdir fs/namei.c:4118 [inline]
__se_sys_mkdir fs/namei.c:4116 [inline]
__x64_sys_mkdir+0x6a/0x80 fs/namei.c:4116
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 (&opts->dep_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
tcm_set_name+0x26/0x90 drivers/usb/gadget/function/f_tcm.c:2224
function_make+0x195/0x350 drivers/usb/gadget/configfs.c:620
configfs_mkdir+0x511/0x9e0 fs/configfs/dir.c:1360
vfs_mkdir+0x386/0x570 fs/namei.c:4073
do_mkdirat+0x1dd/0x5c0 fs/namei.c:4098
__do_sys_mkdir fs/namei.c:4118 [inline]
__se_sys_mkdir fs/namei.c:4116 [inline]
__x64_sys_mkdir+0x6a/0x80 fs/namei.c:4116
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 (gadget_subsys.su_mutex){+.+.}-{3:3}:
check_prev_add kernel/locking/lockdep.c:3053 [inline]
check_prevs_add kernel/locking/lockdep.c:3172 [inline]
validate_chain kernel/locking/lockdep.c:3788 [inline]
__lock_acquire+0x2c66/0x7b50 kernel/locking/lockdep.c:5012
lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
__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
uvcg_frame_dw_frame_interval_store+0xde/0x9c0 drivers/usb/gadget/function/uvc_configfs.c:1336
flush_write_buffer fs/configfs/file.c:207 [inline]
configfs_write_iter+0x30b/0x400 fs/configfs/file.c:229
do_iter_readv_writev+0x47d/0x5f0 fs/read_write.c:-1
do_iter_write+0x1f8/0x7a0 fs/read_write.c:855
vfs_writev fs/read_write.c:928 [inline]
do_writev+0x281/0x480 fs/read_write.c:971
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:
gadget_subsys.su_mutex --> &sb->s_type->i_mutex_key#21 --> &p->frag_sem

Possible unsafe locking scenario:

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

*** DEADLOCK ***

4 locks held by syz.3.1017/8654:
#0: ffff8880284bdc70 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x2bf/0x370 fs/file.c:1056
#1: ffff888145d1e460 (sb_writers#13){.+.+}-{0:0}, at: vfs_writev fs/read_write.c:927 [inline]
#1: ffff888145d1e460 (sb_writers#13){.+.+}-{0:0}, at: do_writev+0x263/0x480 fs/read_write.c:971
#2: ffff88804aaca488 (&buffer->mutex){+.+.}-{3:3}, at: configfs_write_iter+0x7d/0x400 fs/configfs/file.c:226
#3: ffff888025481678 (&p->frag_sem){++++}-{3:3}, at: flush_write_buffer fs/configfs/file.c:205 [inline]
#3: ffff888025481678 (&p->frag_sem){++++}-{3:3}, at: configfs_write_iter+0x20e/0x400 fs/configfs/file.c:229

stack backtrace:
CPU: 1 PID: 8654 Comm: syz.3.1017 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/0x250 lib/dump_stack.c:106
check_noncircular+0x296/0x330 kernel/locking/lockdep.c:2133
check_prev_add kernel/locking/lockdep.c:3053 [inline]
check_prevs_add kernel/locking/lockdep.c:3172 [inline]
validate_chain kernel/locking/lockdep.c:3788 [inline]
__lock_acquire+0x2c66/0x7b50 kernel/locking/lockdep.c:5012
lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
__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
uvcg_frame_dw_frame_interval_store+0xde/0x9c0 drivers/usb/gadget/function/uvc_configfs.c:1336
flush_write_buffer fs/configfs/file.c:207 [inline]
configfs_write_iter+0x30b/0x400 fs/configfs/file.c:229
do_iter_readv_writev+0x47d/0x5f0 fs/read_write.c:-1
do_iter_write+0x1f8/0x7a0 fs/read_write.c:855
vfs_writev fs/read_write.c:928 [inline]
do_writev+0x281/0x480 fs/read_write.c:971
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:0x7f61c36fc0d9
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:00007f61c1954028 EFLAGS: 00000246 ORIG_RAX: 0000000000000014
RAX: ffffffffffffffda RBX: 00007f61c3983fa0 RCX: 00007f61c36fc0d9
RDX: 0000000000000001 RSI: 00002000000005c0 RDI: 0000000000000003
RBP: 00007f61c3793024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f61c3984038 R14: 00007f61c3983fa0 R15: 00007ffd79bfc958
</TASK>


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup