EXT4-fs error (device loop3): __ext4_ext_dirty:182: inode #16: comm kworker/u4:2: mark_inode_dirty error EXT4-fs (loop3): Delayed block allocation failed for inode 16 at logical offset 0 with max blocks 1 with error 117 EXT4-fs (loop3): This should not happen!! Data will be lost EXT4-fs error (device loop3): __ext4_get_inode_loc:4436: comm kworker/u4:2: Invalid inode table block 0 in block_group 0 ================================================================== BUG: KASAN: use-after-free in ext4_ext_binsearch fs/ext4/extents.c:826 [inline] BUG: KASAN: use-after-free in ext4_find_extent+0xbab/0xdb0 fs/ext4/extents.c:945 Read of size 4 at addr ffff8881376906f4 by task kworker/u4:2/31625 CPU: 0 PID: 31625 Comm: kworker/u4:2 Not tainted 5.10.178-syzkaller-00127-g43c801dc3325 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023 Workqueue: writeback wb_workfn (flush-7:3) Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack_lvl+0x1e2/0x24b lib/dump_stack.c:118 print_address_description+0x81/0x3b0 mm/kasan/report.c:248 __kasan_report mm/kasan/report.c:435 [inline] kasan_report+0x179/0x1c0 mm/kasan/report.c:452 __asan_report_load4_noabort+0x14/0x20 mm/kasan/report_generic.c:308 ext4_ext_binsearch fs/ext4/extents.c:826 [inline] ext4_find_extent+0xbab/0xdb0 fs/ext4/extents.c:945 ext4_ext_map_blocks+0x26d/0x6be0 fs/ext4/extents.c:4097 ext4_map_blocks+0xaa7/0x1f00 fs/ext4/inode.c:646 mpage_map_one_extent fs/ext4/inode.c:2450 [inline] mpage_map_and_submit_extent fs/ext4/inode.c:2503 [inline] ext4_writepages+0x148b/0x3c00 fs/ext4/inode.c:2871 do_writepages+0x12e/0x270 mm/page-writeback.c:2358 __writeback_single_inode+0xd7/0xac0 fs/fs-writeback.c:1467 writeback_sb_inodes+0x99c/0x16b0 fs/fs-writeback.c:1730 wb_writeback+0x404/0xc60 fs/fs-writeback.c:1905 wb_do_writeback fs/fs-writeback.c:2050 [inline] wb_workfn+0x3d9/0x1110 fs/fs-writeback.c:2091 process_one_work+0x6dc/0xbd0 kernel/workqueue.c:2298 worker_thread+0xaea/0x1510 kernel/workqueue.c:2444 kthread+0x34b/0x3d0 kernel/kthread.c:313 ret_from_fork+0x1f/0x30 :299 The buggy address belongs to the page: page:ffffea0004dda400 refcount:0 mapcount:-128 mapping:0000000000000000 index:0x1 pfn:0x137690 flags: 0x4000000000000000() raw: 4000000000000000 ffffea0004f91a08 ffffea0005d21808 0000000000000000 raw: 0000000000000001 0000000000000002 00000000ffffff7f 0000000000000000 page dumped because: kasan: bad access detected page_owner tracks the page as freed page last allocated via order 0, migratetype Movable, gfp_mask 0x101cca(GFP_HIGHUSER_MOVABLE|__GFP_WRITE), pid 1418, ts 2326558436125, free_ts 2326814933765 set_page_owner include/linux/page_owner.h:35 [inline] post_alloc_hook mm/page_alloc.c:2455 [inline] prep_new_page+0x166/0x180 mm/page_alloc.c:2461 get_page_from_freelist+0x2d8c/0x2f30 mm/page_alloc.c:4253 __alloc_pages_nodemask+0x435/0xaf0 mm/page_alloc.c:5345 __alloc_pages include/linux/gfp.h:544 [inline] __alloc_pages_node include/linux/gfp.h:557 [inline] alloc_pages_node include/linux/gfp.h:571 [inline] alloc_pages include/linux/gfp.h:590 [inline] __page_cache_alloc include/linux/pagemap.h:290 [inline] pagecache_get_page+0x669/0x950 mm/filemap.c:1848 grab_cache_page_write_begin+0x5d/0xa0 mm/filemap.c:3451 ext4_da_write_begin+0x587/0xf60 fs/ext4/inode.c:3065 generic_perform_write+0x2cd/0x570 mm/filemap.c:3501 ext4_buffered_write_iter+0x47d/0x610 fs/ext4/file.c:272 ext4_file_write_iter+0x193/0x1ca0 fs/ext4/file.c:689 call_write_iter include/linux/fs.h:1976 [inline] new_sync_write fs/read_write.c:518 [inline] vfs_write+0xb55/0xe70 fs/read_write.c:605 ksys_write+0x199/0x2c0 fs/read_write.c:658 __do_sys_write fs/read_write.c:670 [inline] __se_sys_write fs/read_write.c:667 [inline] __x64_sys_write+0x7b/0x90 fs/read_write.c:667 do_syscall_64+0x34/0x70 entry_SYSCALL_64_after_hwframe+0x61/0xc6 page last free stack trace: reset_page_owner include/linux/page_owner.h:28 [inline] free_pages_prepare mm/page_alloc.c:1348 [inline] free_pcp_prepare mm/page_alloc.c:1420 [inline] free_unref_page_prepare+0x2ae/0x2d0 mm/page_alloc.c:3335 free_unref_page_list+0x122/0xb20 mm/page_alloc.c:3442 release_pages+0xea0/0xef0 mm/swap.c:1103 __pagevec_release+0x84/0x100 mm/swap.c:1123 pagevec_release include/linux/pagevec.h:88 [inline] truncate_inode_pages_range+0xa81/0x1ae0 mm/truncate.c:367 truncate_inode_pages mm/truncate.c:473 [inline] truncate_inode_pages_final+0xc1/0xd0 mm/truncate.c:524 ext4_evict_inode+0x4e0/0x1730 fs/ext4/inode.c:225 evict+0x2a3/0x6c0 fs/inode.c:577 iput_final fs/inode.c:1655 [inline] iput+0x632/0x7e0 fs/inode.c:1681 do_unlinkat+0x48e/0x8b0 fs/namei.c:4048 __do_sys_unlink fs/namei.c:4088 [inline] __se_sys_unlink fs/namei.c:4086 [inline] __x64_sys_unlink+0x49/0x50 fs/namei.c:4086 do_syscall_64+0x34/0x70 entry_SYSCALL_64_after_hwframe+0x61/0xc6 Memory state around the buggy address: ffff888137690580: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff888137690600: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >ffff888137690680: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ^ ffff888137690700: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff888137690780: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ================================================================== EXT4-fs error (device loop3): ext4_ext_split:1071: inode #18: comm kworker/u4:2: p_ext > EXT_MAX_EXTENT! EXT4-fs (loop3): Delayed block allocation failed for inode 18 at logical offset 0 with max blocks 15 with error 117 EXT4-fs (loop3): This should not happen!! Data will be lost EXT4-fs error (device loop3): __ext4_get_inode_loc:4436: comm kworker/u4:2: Invalid inode table block 0 in block_group 0