EXT4-fs error (device loop0): ext4_read_block_bitmap_nowait:476: comm syz-executor.0: Invalid block bitmap block 0 in block_group 0 EXT4-fs (loop0): Remounting filesystem read-only EXT4-fs error (device loop0) in ext4_mb_clear_bb:6150: Corrupt filesystem ================================================================== BUG: KASAN: out-of-bounds in ext4_ext_rm_leaf fs/ext4/extents.c:2735 [inline] BUG: KASAN: out-of-bounds in ext4_ext_remove_space+0x2149/0x4a60 fs/ext4/extents.c:2957 Read of size 18446744073709551544 at addr ffff88812459e054 by task syz-executor.0/362 CPU: 1 PID: 362 Comm: syz-executor.0 Not tainted 5.15.148-syzkaller-1069047-g993bed180178 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x151/0x1b7 lib/dump_stack.c:106 print_address_description+0x87/0x3b0 mm/kasan/report.c:248 __kasan_report mm/kasan/report.c:427 [inline] kasan_report+0x179/0x1c0 mm/kasan/report.c:444 kasan_check_range+0x293/0x2a0 mm/kasan/generic.c:189 memmove+0x2d/0x70 mm/kasan/shadow.c:54 ext4_ext_rm_leaf fs/ext4/extents.c:2735 [inline] ext4_ext_remove_space+0x2149/0x4a60 fs/ext4/extents.c:2957 ext4_punch_hole+0x794/0xbf0 fs/ext4/inode.c:4119 ext4_fallocate+0x30c/0x1f10 fs/ext4/extents.c:4711 vfs_fallocate+0x492/0x570 fs/open.c:309 do_vfs_ioctl+0x2238/0x2a80 fs/ioctl.c:853 __do_sys_ioctl fs/ioctl.c:872 [inline] __se_sys_ioctl+0x99/0x190 fs/ioctl.c:860 __x64_sys_ioctl+0x7b/0x90 fs/ioctl.c:860 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x61/0xcb RIP: 0033:0x7f99a5e8bae9 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:00007f999d62d0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f99a5fab050 RCX: 00007f99a5e8bae9 RDX: 0000000020000080 RSI: 000000004030582b RDI: 0000000000000004 RBP: 00007f99a5ed747a R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 000000000000000b R14: 00007f99a5fab050 R15: 00007fff51a4e668 The buggy address belongs to the page: page:ffffea0004916780 refcount:2 mapcount:0 mapping:ffff888109195b18 index:0x3a pfn:0x12459e memcg:ffff888117f2c000 aops:def_blk_aops ino:700000 flags: 0x4000000000002036(referenced|uptodate|lru|active|private|zone=1) raw: 4000000000002036 ffffea0004916d08 ffffea00046bf9c8 ffff888109195b18 raw: 000000000000003a ffff88811d3b72a0 00000002ffffffff ffff888117f2c000 page dumped because: kasan: bad access detected page_owner tracks the page as allocated page last allocated via order 0, migratetype Movable, gfp_mask 0x108c48(GFP_NOFS|__GFP_NOFAIL|__GFP_HARDWALL|__GFP_MOVABLE), pid 358, ts 42270886210, free_ts 42200533639 set_page_owner include/linux/page_owner.h:33 [inline] post_alloc_hook+0x1a3/0x1b0 mm/page_alloc.c:2604 prep_new_page+0x1b/0x110 mm/page_alloc.c:2610 get_page_from_freelist+0x3550/0x35d0 mm/page_alloc.c:4484 __alloc_pages+0x27e/0x8f0 mm/page_alloc.c:5776 __alloc_pages_node include/linux/gfp.h:591 [inline] alloc_pages_node include/linux/gfp.h:605 [inline] alloc_pages include/linux/gfp.h:618 [inline] __page_cache_alloc include/linux/pagemap.h:305 [inline] pagecache_get_page+0xb18/0xeb0 mm/filemap.c:1940 find_or_create_page include/linux/pagemap.h:418 [inline] grow_dev_page fs/buffer.c:949 [inline] grow_buffers fs/buffer.c:1014 [inline] __getblk_slow fs/buffer.c:1041 [inline] __getblk_gfp+0x21e/0x7c0 fs/buffer.c:1336 sb_getblk_gfp include/linux/buffer_head.h:368 [inline] ext4_ext_grow_indepth fs/ext4/extents.c:1328 [inline] ext4_ext_create_new_leaf fs/ext4/extents.c:1429 [inline] ext4_ext_insert_extent+0xf7a/0x4b10 fs/ext4/extents.c:2099 ext4_ext_map_blocks+0x1c61/0x7250 fs/ext4/extents.c:4308 ext4_map_blocks+0xaa7/0x1e00 fs/ext4/inode.c:646 _ext4_get_block+0x23b/0x660 fs/ext4/inode.c:793 ext4_get_block+0x39/0x50 fs/ext4/inode.c:810 ext4_block_write_begin+0x5ea/0x12a0 fs/ext4/inode.c:1078 ext4_write_begin+0x6bc/0x13d0 ext4_da_write_begin+0x4a2/0xc30 fs/ext4/inode.c:2976 generic_perform_write+0x2bc/0x5a0 mm/filemap.c:3843 ext4_buffered_write_iter+0x48a/0x610 fs/ext4/file.c:270 page last free stack trace: reset_page_owner include/linux/page_owner.h:26 [inline] free_pages_prepare mm/page_alloc.c:1471 [inline] free_pcp_prepare mm/page_alloc.c:1543 [inline] free_unref_page_prepare+0x7c8/0x7d0 mm/page_alloc.c:3533 free_unref_page_list+0x14b/0xa60 mm/page_alloc.c:3670 release_pages+0x1310/0x1370 mm/swap.c:1009 __pagevec_release+0x84/0x100 mm/swap.c:1029 pagevec_release include/linux/pagevec.h:81 [inline] shmem_undo_range+0x604/0x1560 mm/shmem.c:965 shmem_truncate_range mm/shmem.c:1064 [inline] shmem_evict_inode+0x215/0x9d0 mm/shmem.c:1146 evict+0x2a3/0x630 fs/inode.c:587 iput_final fs/inode.c:1705 [inline] iput+0x63b/0x7e0 fs/inode.c:1731 dentry_unlink_inode+0x34f/0x440 fs/dcache.c:376 __dentry_kill+0x447/0x660 fs/dcache.c:582 dentry_kill+0xc0/0x2a0 dput+0x165/0x320 fs/dcache.c:888 __fput+0x662/0x910 fs/file_table.c:288 ____fput+0x15/0x20 fs/file_table.c:308 task_work_run+0x129/0x190 kernel/task_work.c:164 tracehook_notify_resume include/linux/tracehook.h:189 [inline] exit_to_user_mode_loop+0xc4/0xe0 kernel/entry/common.c:175 Memory state around the buggy address: ffff88812459df00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff88812459df80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >ffff88812459e000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ^ ffff88812459e080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff88812459e100: 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:4340: comm syz-executor.0: Invalid inode table block 0 in block_group 0 EXT4-fs error (device loop0) in ext4_reserve_inode_write:5820: Corrupt filesystem EXT4-fs error (device loop0): ext4_punch_hole:4132: inode #16: comm syz-executor.0: mark_inode_dirty error