[v5.15] WARNING: still has locks held in __se_sys_io_uring_enter

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 68efe5a6c16a Linux 5.15.197
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14b58d58580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7e6ed99963d6ee1d
dashboard link: https://syzkaller.appspot.com/bug?extid=15c7432d3879350ea13a
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/900f9b9bd850/disk-68efe5a6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1e089a5019a6/vmlinux-68efe5a6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b319f477b907/bzImage-68efe5a6.xz

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

====================================
WARNING: syz.8.1328/10779 still has locks held!
syzkaller #0 Not tainted
------------------------------------
1 lock held by syz.8.1328/10779:
#0: ffff88807273a0a8 (&ctx->uring_lock){+.+.}-{3:3}, at: __do_sys_io_uring_enter io_uring/io_uring.c:10115 [inline]
#0: ffff88807273a0a8 (&ctx->uring_lock){+.+.}-{3:3}, at: __se_sys_io_uring_enter+0x262/0x1d30 io_uring/io_uring.c:10058

stack backtrace:
CPU: 0 PID: 10779 Comm: syz.8.1328 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Call Trace:
<TASK>
dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
try_to_freeze include/linux/freezer.h:66 [inline]
freezer_count include/linux/freezer.h:128 [inline]
freezable_schedule_timeout include/linux/freezer.h:193 [inline]
unix_stream_data_wait net/unix/af_unix.c:2477 [inline]
unix_stream_read_generic+0x1894/0x2360 net/unix/af_unix.c:2700
__unix_stream_recvmsg+0xe3/0x130 net/unix/af_unix.c:2845
__unix_recvmsg net/unix/unix_bpf.c:47 [inline]
unix_bpf_recvmsg+0xbc5/0xd40 net/unix/unix_bpf.c:-1
unix_stream_recvmsg+0x144/0x1b0 net/unix/af_unix.c:2864
sock_recvmsg_nosec net/socket.c:968 [inline]
sock_recvmsg net/socket.c:986 [inline]
sock_read_iter+0x2a2/0x340 net/socket.c:1067
call_read_iter include/linux/fs.h:2167 [inline]
io_iter_do_read io_uring/io_uring.c:3575 [inline]
io_read io_uring/io_uring.c:3638 [inline]
io_issue_sqe+0x2bd1/0xa6a0 io_uring/io_uring.c:6922
__io_queue_sqe+0x34/0x360 io_uring/io_uring.c:7244
io_queue_sqe io_uring/io_uring.c:7295 [inline]
io_submit_sqe io_uring/io_uring.c:7472 [inline]
io_submit_sqes+0x594a/0x9b00 io_uring/io_uring.c:7580
__do_sys_io_uring_enter io_uring/io_uring.c:10116 [inline]
__se_sys_io_uring_enter+0x26d/0x1d30 io_uring/io_uring.c:10058
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:0x7f6e2314a749
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f6e213b1038 EFLAGS: 00000246 ORIG_RAX: 00000000000001aa
RAX: ffffffffffffffda RBX: 00007f6e233a0fa0 RCX: 00007f6e2314a749
RDX: 0000000000000000 RSI: 00000000100847c0 RDI: 0000000000000007
RBP: 00007f6e231cef91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f6e233a1038 R14: 00007f6e233a0fa0 R15: 00007fff866be968
</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

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: 68efe5a6c16a Linux 5.15.197
git tree: linux-5.15.y

console output: https://syzkaller.appspot.com/x/log.txt?x=1206b9b4580000

kernel config: https://syzkaller.appspot.com/x/.config?x=7e6ed99963d6ee1d
dashboard link: https://syzkaller.appspot.com/bug?extid=15c7432d3879350ea13a
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10838d58580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12197184580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/900f9b9bd850/disk-68efe5a6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1e089a5019a6/vmlinux-68efe5a6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b319f477b907/bzImage-68efe5a6.xz

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

====================================

WARNING: syz.0.17/4330 still has locks held!

syzkaller #0 Not tainted
------------------------------------

1 lock held by syz.0.17/4330:
#0: ffff88807de820a8 (&ctx->uring_lock){+.+.}-{3:3}, at: __do_sys_io_uring_enter io_uring/io_uring.c:10115 [inline]
#0: ffff88807de820a8 (&ctx->uring_lock){+.+.}-{3:3}, at: __se_sys_io_uring_enter+0x262/0x1d30 io_uring/io_uring.c:10058

stack backtrace:
CPU: 0 PID: 4330 Comm: syz.0.17 Not tainted syzkaller #0

RIP: 0033:0x7fa44eb17749

Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48

RSP: 002b:00007fff74bd9e08 EFLAGS: 00000246 ORIG_RAX: 00000000000001aa
RAX: ffffffffffffffda RBX: 00007fa44ed6dfa0 RCX: 00007fa44eb17749

RDX: 0000000000000000 RSI: 00000000100847c0 RDI: 0000000000000007

RBP: 00007fa44eb9bf91 R08: 0000000000000000 R09: 0000000000000000

R10: 0000000000000001 R11: 0000000000000246 R12: 0000000000000000

R13: 00007fa44ed6dfa0 R14: 00007fa44ed6dfa0 R15: 0000000000000006
</TASK>


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.