EXT4-fs (loop0): Remounting filesystem read-only
EXT4-fs error (device loop0) in ext4_mb_clear_bb:6137: Corrupt filesystem
==================================================================
BUG: KASAN: out-of-bounds in ext4_ext_rm_leaf fs/ext4/extents.c:2737 [inline]
BUG: KASAN: out-of-bounds in ext4_ext_remove_space+0x1e16/0x4f50 fs/ext4/extents.c:2959
Read of size 18446744073709551544 at addr ffff88812923f054 by task syz-executor.0/357

CPU: 1 PID: 357 Comm: syz-executor.0 Not tainted 6.1.75-syzkaller-1150975-gcfa154389a65 #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+0x151/0x1b7 lib/dump_stack.c:106
 print_address_description mm/kasan/report.c:316 [inline]
 print_report+0x158/0x4e0 mm/kasan/report.c:427
 kasan_report+0x13c/0x170 mm/kasan/report.c:531
 kasan_check_range+0x294/0x2a0 mm/kasan/generic.c:189
 memmove+0x2d/0x70 mm/kasan/shadow.c:54
 ext4_ext_rm_leaf fs/ext4/extents.c:2737 [inline]
 ext4_ext_remove_space+0x1e16/0x4f50 fs/ext4/extents.c:2959
 ext4_punch_hole+0x794/0xc00 fs/ext4/inode.c:4129
 ext4_fallocate+0x318/0x1e90 fs/ext4/extents.c:4708
 vfs_fallocate+0x492/0x570 fs/open.c:324
 do_vfs_ioctl+0x2150/0x29a0 fs/ioctl.c:849
 __do_sys_ioctl fs/ioctl.c:868 [inline]
 __se_sys_ioctl+0x99/0x190 fs/ioctl.c:856
 __x64_sys_ioctl+0x7b/0x90 fs/ioctl.c:856
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f1d2427cae9
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:00007f1d24ef70c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f1d2439c050 RCX: 00007f1d2427cae9
RDX: 0000000020000080 RSI: 000000004030582b RDI: 0000000000000004
RBP: 00007f1d242c847a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f1d2439c050 R15: 00007fff64ec8e68
 </TASK>

The buggy address belongs to the physical page:
page:ffffea0004a48fc0 refcount:2 mapcount:0 mapping:ffff88810b831c50 index:0x3a pfn:0x12923f
memcg:ffff888109d50000
aops:def_blk_aops ino:700000
flags: 0x5600000000002056(referenced|uptodate|lru|workingset|private|zone=1)
raw: 5600000000002056 ffffea0004a48688 ffffea00043c9308 ffff88810b831c50
raw: 000000000000003a ffff888121565150 00000002ffffffff ffff888109d50000
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 0, migratetype Movable, gfp_mask 0x148c48(GFP_NOFS|__GFP_NOFAIL|__GFP_COMP|__GFP_HARDWALL|__GFP_MOVABLE), pid 352, tgid 351 (syz-executor.0), ts 39639406536, free_ts 0
 set_page_owner include/linux/page_owner.h:33 [inline]
 post_alloc_hook+0x213/0x220 mm/page_alloc.c:2590
 prep_new_page+0x1b/0x110 mm/page_alloc.c:2597
 get_page_from_freelist+0x27ea/0x2870 mm/page_alloc.c:4425
 __alloc_pages+0x3a1/0x780 mm/page_alloc.c:5712
 __folio_alloc+0x15/0x40 mm/page_alloc.c:5744
 __folio_alloc_node include/linux/gfp.h:245 [inline]
 folio_alloc include/linux/gfp.h:274 [inline]
 filemap_alloc_folio include/linux/pagemap.h:507 [inline]
 __filemap_get_folio+0x827/0xae0 mm/filemap.c:1983
 pagecache_get_page+0x2f/0x110 mm/folio-compat.c:110
 find_or_create_page include/linux/pagemap.h:648 [inline]
 grow_dev_page fs/buffer.c:989 [inline]
 grow_buffers fs/buffer.c:1054 [inline]
 __getblk_slow fs/buffer.c:1081 [inline]
 __getblk_gfp+0x205/0x7d0 fs/buffer.c:1376
 sb_getblk_gfp include/linux/buffer_head.h:363 [inline]
 ext4_ext_grow_indepth fs/ext4/extents.c:1334 [inline]
 ext4_ext_create_new_leaf fs/ext4/extents.c:1435 [inline]
 ext4_ext_insert_extent+0xfd2/0x4e00 fs/ext4/extents.c:2102
 ext4_ext_map_blocks+0x1c31/0x71e0 fs/ext4/extents.c:4308
 ext4_map_blocks+0xa36/0x1ca0 fs/ext4/inode.c:651
 _ext4_get_block+0x23b/0x660 fs/ext4/inode.c:798
 ext4_get_block+0x39/0x50 fs/ext4/inode.c:815
 ext4_block_write_begin+0x55e/0x1200 fs/ext4/inode.c:1100
 ext4_write_begin+0x5e0/0xfb0
 ext4_da_write_begin+0x2ff/0x920 fs/ext4/inode.c:2989
page_owner free stack trace missing

Memory state around the buggy address:
 ffff88812923ef00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff88812923ef80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>ffff88812923f000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
                                                 ^
 ffff88812923f080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff88812923f100: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================
EXT4-fs error (device loop0): __ext4_get_inode_loc:4497: comm syz-executor.0: Invalid inode table block 0 in block_group 0
EXT4-fs error (device loop0) in ext4_reserve_inode_write:5870: Corrupt filesystem
EXT4-fs error (device loop0): ext4_punch_hole:4142: inode #16: comm syz-executor.0: mark_inode_dirty error