[v5.15] KASAN: stack-out-of-bounds Read in gfs2_file_read_iter (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c52b9710c83d Linux 5.15.156
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=168ff5f7180000
kernel config: https://syzkaller.appspot.com/x/.config?x=567b6ddc38438433
dashboard link: https://syzkaller.appspot.com/bug?extid=0e28304b093273945196
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1bd4b9969373/disk-c52b9710.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/10509e89bd25/vmlinux-c52b9710.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a623a4c52eb5/bzImage-c52b9710.xz

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

gfs2: fsid=�ȭ����ujV�g��J �!}.0: found 1 quota changes
==================================================================
BUG: KASAN: stack-out-of-bounds in should_fault_in_pages fs/gfs2/file.c:784 [inline]
BUG: KASAN: stack-out-of-bounds in gfs2_file_read_iter+0x938/0xe40 fs/gfs2/file.c:994
Read of size 8 at addr ffffc90004007d30 by task syz-executor.4/3667

CPU: 0 PID: 3667 Comm: syz-executor.4 Not tainted 5.15.156-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2d0 lib/dump_stack.c:106
print_address_description+0x63/0x3b0 mm/kasan/report.c:248
__kasan_report mm/kasan/report.c:434 [inline]
kasan_report+0x16b/0x1c0 mm/kasan/report.c:451
should_fault_in_pages fs/gfs2/file.c:784 [inline]
gfs2_file_read_iter+0x938/0xe40 fs/gfs2/file.c:994
call_read_iter include/linux/fs.h:2166 [inline]
new_sync_read fs/read_write.c:404 [inline]
vfs_read+0xa9f/0xe10 fs/read_write.c:485
ksys_read+0x1a2/0x2c0 fs/read_write.c:623
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f281b17dea9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f28196f00c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
RAX: ffffffffffffffda RBX: 00007f281b2abf80 RCX: 00007f281b17dea9
RDX: 0000000000002020 RSI: 00000000200028c0 RDI: 0000000000000004
RBP: 00007f281b1ca4a4 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f281b2abf80 R15: 00007ffd3bf17288
</TASK>


addr ffffc90004007d30 is located in stack of task syz-executor.4/3667 at offset 48 in frame:
vfs_read+0x0/0xe10

this frame has 3 objects:
[32, 48) 'iov.i'
[64, 112) 'kiocb.i'
[144, 184) 'iter.i'

Memory state around the buggy address:
ffffc90004007c00: 00 00 00 f3 f3 f3 f3 f3 00 00 00 00 00 00 00 00
ffffc90004007c80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffffc90004007d00: f1 f1 f1 f1 00 00 f2 f2 00 00 00 00 00 00 f2 f2
^
ffffc90004007d80: f2 f2 00 00 00 00 00 f3 f3 f3 f3 f3 00 00 00 00
ffffc90004007e00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================


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