[v5.15] linux-5.15.y test error: Internal error in lookup_ioctx

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 01879f56bdde Linux 5.15.190
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10e83c62580000
kernel config: https://syzkaller.appspot.com/x/.config?x=77d41448639e880c
dashboard link: https://syzkaller.appspot.com/bug?extid=7bc2b1c6268d7ff840ed
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
userspace arch: arm64

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a0589d1700cf/disk-01879f56.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9129cd9481e7/vmlinux-01879f56.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ddf23639d805/Image-01879f56.gz.xz

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

Internal error: Oops - BTI: 0000000036000001 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 4165 Comm: syz.2.117 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/30/2025
pstate: 42400405 (nZcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=jc)
pc : lookup_ioctx+0x108/0x7d0 fs/aio.c:1070
lr : lookup_ioctx+0xe4/0x7d0 fs/aio.c:1070
sp : ffff80001f907c20
x29: ffff80001f907c20 x28: ffff0000c21f3680 x27: 0000000020000000
x26: 1fffe0001843e6d0 x25: 1ffff00003f20fd6 x24: ffff0000ce53bf40
x23: dfff800000000000 x22: 00000000fffffff2 x21: 0000000000000000
x20: ffff0000c21f3680 x19: 0000000000000000 x18: 0000000000000000
x17: 0000000000000000 x16: ffff800008a19ff4 x15: 0000000000000000
x14: 0000000000000000 x13: 1ffff0000283006b x12: 0000000000ff0100
x11: 0000000000000000 x10: 0000000000000000 x9 : 0000ffffffffffff
x8 : 0000000000000000 x7 : ffff80000875120c x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000001
x2 : 0000000000000008 x1 : 0000000000000001 x0 : 0000000000000000
Call trace:
lookup_ioctx+0x108/0x7d0 fs/aio.c:1070
__do_sys_io_submit fs/aio.c:2053 [inline]
__se_sys_io_submit fs/aio.c:2042 [inline]
__arm64_sys_io_submit+0x110/0x40c fs/aio.c:2042
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: d503229f 2a1f03f6 2a1f03e0 b8400953 (2a1603e1)
---[ end trace 39972d3c15d52616 ]---
----------------
Code disassembly (best guess):
0: d503229f csdb
4: 2a1f03f6 mov w22, wzr
8: 2a1f03e0 mov w0, wzr
c: b8400953 ldtr w19, [x10]
* 10: 2a1603e1 mov w1, w22 <-- trapping instruction


---
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