ci2 starts bisection 2025-09-13 16:53:48.203159577 +0000 UTC m=+164340.077974704 bisecting fixing commit since 6de38b5f6c2b4da6703115c17f7d8814b93b735c building syzkaller on 7117feecc9626dc60b06fb3e91c0f7632d99d30b ensuring issue is reproducible on original commit 6de38b5f6c2b4da6703115c17f7d8814b93b735c testing commit 6de38b5f6c2b4da6703115c17f7d8814b93b735c gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: 74c16be144c77d5ad906edb50e494ce68f73c41d55d16233f5799141472c7a18 run #0: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #1: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #2: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #3: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #4: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #5: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #6: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #7: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #8: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #9: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #10: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #11: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #12: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #13: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #14: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #15: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #16: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #17: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #18: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #19: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data representative crash: KASAN: slab-out-of-bounds Read in ext4_read_inline_data, types: [KASAN-READ KASAN-USE-AFTER-FREE-READ] check whether we can drop unnecessary instrumentation disabling configs for [atomic_sleep hang memleak ubsan bug_or_warning locking], they are not needed testing commit 6de38b5f6c2b4da6703115c17f7d8814b93b735c gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: e7faa49a1e07f5f1d199bbb3ca9027ef0636935c93ed3b895c3ae800689464b3 run #0: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #1: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #2: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #3: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #4: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #5: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #6: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #7: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #8: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #9: crashed: KASAN: use-after-free Read in ext4_read_inline_data representative crash: KASAN: slab-out-of-bounds Read in ext4_read_inline_data, types: [KASAN-READ KASAN-USE-AFTER-FREE-READ] the bug reproduces without the instrumentation disabling configs for [bug_or_warning locking atomic_sleep hang memleak ubsan], they are not needed kconfig minimization: base=4788 full=6024 leaves diff=246 split chunks (needed=false): <246> split chunk #0 of len 246 into 5 parts testing without sub-chunk 1/5 disabling configs for [hang memleak ubsan bug_or_warning locking atomic_sleep], they are not needed testing commit 6de38b5f6c2b4da6703115c17f7d8814b93b735c gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: 7d9f7d22054ea10193f30f1fc35f4684c158505d50fe3c133f4371b509911076 run #0: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #1: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #2: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #3: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #4: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #5: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #6: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #7: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #8: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #9: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data representative crash: KASAN: use-after-free Read in ext4_read_inline_data, types: [KASAN-USE-AFTER-FREE-READ KASAN-READ] the chunk can be dropped testing without sub-chunk 2/5 disabling configs for [bug_or_warning locking atomic_sleep hang memleak ubsan], they are not needed testing commit 6de38b5f6c2b4da6703115c17f7d8814b93b735c gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: e13e2199cce484027d0a2eee9c0ac17b0afa408c252fb244ad04da9035dc707d run #0: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #1: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #2: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #3: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #4: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #5: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #6: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #7: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #8: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #9: crashed: KASAN: use-after-free Read in ext4_read_inline_data representative crash: KASAN: use-after-free Read in ext4_read_inline_data, types: [KASAN-USE-AFTER-FREE-READ KASAN-READ] the chunk can be dropped testing without sub-chunk 3/5 disabling configs for [hang memleak ubsan bug_or_warning locking atomic_sleep], they are not needed testing commit 6de38b5f6c2b4da6703115c17f7d8814b93b735c gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: ddaf4e124f9ae49f39b769d2684003601f87cfc4a09a2514cb38a29299bbe4cc run #0: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #1: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #2: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #3: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #4: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #5: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #6: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #7: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #8: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #9: crashed: KASAN: use-after-free Read in ext4_read_inline_data representative crash: KASAN: use-after-free Read in ext4_read_inline_data, types: [KASAN-USE-AFTER-FREE-READ] the chunk can be dropped testing without sub-chunk 4/5 disabling configs for [bug_or_warning locking atomic_sleep hang memleak ubsan], they are not needed testing commit 6de38b5f6c2b4da6703115c17f7d8814b93b735c gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: fd118dd79c03c6d1e3f22ff20805c5f9694c5b3881825e4c8a86c2541fc705b2 run #0: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #1: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #2: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #3: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #4: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #5: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #6: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #7: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #8: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #9: crashed: KASAN: use-after-free Read in ext4_read_inline_data representative crash: KASAN: use-after-free Read in ext4_read_inline_data, types: [KASAN-USE-AFTER-FREE-READ] the chunk can be dropped testing without sub-chunk 5/5 disabling configs for [bug_or_warning locking atomic_sleep hang memleak ubsan], they are not needed testing commit 6de38b5f6c2b4da6703115c17f7d8814b93b735c gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.40 failed building 6de38b5f6c2b4da6703115c17f7d8814b93b735c: net/socket.c:1128: undefined reference to `wext_handle_ioctl' net/socket.c:3397: undefined reference to `compat_wext_handle_ioctl' net/core/net-procfs.c:346: undefined reference to `wext_proc_exit' net/core/net-procfs.c:330: undefined reference to `wext_proc_init' minimized to 46 configs; suspects: [HID_ZEROPLUS USB_NET_GL620A USB_NET_MCS7830 USB_NET_NET1080 USB_NET_PLUSB USB_NET_RNDIS_HOST USB_NET_SMSC75XX USB_NET_SMSC95XX USB_NET_SR9700 USB_NET_SR9800 USB_NET_ZAURUS USB_OHCI_HCD USB_OHCI_HCD_PCI USB_OHCI_HCD_PLATFORM USB_OTG USB_OTG_FSM USB_PRINTER USB_SERIAL USB_SERIAL_FTDI_SIO USB_SERIAL_GENERIC USB_SERIAL_PL2303 USB_STORAGE_ALAUDA USB_STORAGE_CYPRESS_ATACB USB_STORAGE_DATAFAB USB_STORAGE_FREECOM USB_STORAGE_ISD200 USB_STORAGE_JUMPSHOT USB_STORAGE_KARMA USB_STORAGE_ONETOUCH USB_STORAGE_SDDR09 USB_STORAGE_SDDR55 USB_STORAGE_USBAT USB_TRANCEVIBRATOR USB_U_AUDIO USB_U_ETHER USB_U_SERIAL USB_WDM USB_XHCI_PCI_RENESAS WLAN WLAN_VENDOR_ATH WLAN_VENDOR_ATMEL WLAN_VENDOR_BROADCOM WLAN_VENDOR_INTERSIL WLAN_VENDOR_MARVELL WLAN_VENDOR_MEDIATEK WLAN_VENDOR_MICROCHIP WLAN_VENDOR_RALINK WLAN_VENDOR_REALTEK WLAN_VENDOR_RSI WLAN_VENDOR_ZYDAS ZEROPLUS_FF] disabling configs for [bug_or_warning locking atomic_sleep hang memleak ubsan], they are not needed testing current HEAD 911f602c2237b4e5cad1e1f53bfcf6190a37a764 testing commit 911f602c2237b4e5cad1e1f53bfcf6190a37a764 gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: 11f470e1deaef96e3814258f67e600e9887c591b89e0073cb3921dda56fb2fbf run #0: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #1: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #2: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #3: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #4: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #5: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #6: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #7: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #8: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #9: crashed: KASAN: use-after-free Read in ext4_read_inline_data representative crash: KASAN: use-after-free Read in ext4_read_inline_data, types: [KASAN-USE-AFTER-FREE-READ KASAN-READ] crash still not fixed/happens on the oldest tested release revisions tested: 7, total time: 2h0m5.278408958s (build: 44m3.996307592s, test: 46m51.47621893s) crash still not fixed or there were kernel test errors commit msg: Merge 5.10.244 into android13-5.10-lts crash: KASAN: use-after-free Read in ext4_read_inline_data EXT4-fs error (device loop5): ext4_xattr_ibody_find:2219: inode #12: comm syz-executor: corrupted in-inode xattr ================================================================== BUG: KASAN: use-after-free in ext4_read_inline_data fs/ext4/inline.c:209 [inline] BUG: KASAN: use-after-free in ext4_read_inline_data+0x1f3/0x2d0 fs/ext4/inline.c:177 Read of size 68 at addr ffff8881289c46d3 by task syz-executor/437 CPU: 1 PID: 437 Comm: syz-executor Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/14/2025 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack_lvl+0x81/0xac lib/dump_stack.c:118 print_address_description.constprop.0+0x24/0x160 mm/kasan/report.c:248 __kasan_report mm/kasan/report.c:435 [inline] kasan_report.cold+0x82/0xdb mm/kasan/report.c:452 check_region_inline mm/kasan/generic.c:183 [inline] kasan_check_range+0x148/0x190 mm/kasan/generic.c:189 memcpy+0x24/0x60 mm/kasan/shadow.c:65 ext4_read_inline_data fs/ext4/inline.c:209 [inline] ext4_read_inline_data+0x1f3/0x2d0 fs/ext4/inline.c:177 ext4_read_inline_dir+0x25c/0xda0 fs/ext4/inline.c:1523 ext4_readdir+0x5c1/0x3020 fs/ext4/dir.c:161 iterate_dir+0x407/0x690 fs/readdir.c:65 __do_sys_getdents64 fs/readdir.c:369 [inline] __se_sys_getdents64 fs/readdir.c:354 [inline] __x64_sys_getdents64+0x12f/0x230 fs/readdir.c:354 do_syscall_64+0x32/0x50 arch/x86/entry/common.c:46 entry_SYSCALL_64_after_hwframe+0x61/0xcb RIP: 0033:0x7f414765b313 Code: c1 66 0f 1f 44 00 00 48 83 c4 08 48 89 ef 5b 5d e9 62 3e f8 ff 66 90 b8 ff ff ff 7f 48 39 c2 48 0f 47 d0 b8 d9 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 05 c3 0f 1f 40 00 48 c7 c2 a8 ff ff ff f7 d8 RSP: 002b:00007fff5b291208 EFLAGS: 00000293 ORIG_RAX: 00000000000000d9 RAX: ffffffffffffffda RBX: 0000555558695520 RCX: 00007f414765b313 RDX: 0000000000008000 RSI: 0000555558695520 RDI: 0000000000000006 RBP: 00005555586954f4 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000001000 R11: 0000000000000293 R12: ffffffffffffffa8 R13: 0000000000000016 R14: 00005555586954f0 R15: 00007fff5b2945b0 The buggy address belongs to the page: page:ffffea0004a27100 refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x1289c4 flags: 0x4000000000000000() raw: 4000000000000000 ffffea0004a270c8 ffffea0004a27148 0000000000000000 raw: 0000000000000001 0000000000000000 00000000ffffffff 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 0x8100dca(GFP_HIGHUSER_MOVABLE|__GFP_ZERO|0x8000000), pid 401, ts 79479853355, free_ts 79480712371 set_page_owner include/linux/page_owner.h:35 [inline] post_alloc_hook mm/page_alloc.c:2456 [inline] prep_new_page mm/page_alloc.c:2462 [inline] get_page_from_freelist+0x1fee/0x2ad0 mm/page_alloc.c:4254 __alloc_pages_nodemask+0x2ae/0x2530 mm/page_alloc.c:5370 __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] do_anonymous_page mm/memory.c:3963 [inline] handle_pte_fault+0x1672/0x3210 mm/memory.c:4786 __handle_mm_fault+0xac7/0xfa0 mm/memory.c:4944 handle_mm_fault+0x1b8/0x6b0 mm/memory.c:5358 do_user_addr_fault+0x4d0/0xa20 arch/x86/mm/fault.c:1362 handle_page_fault arch/x86/mm/fault.c:1428 [inline] exc_page_fault+0x65/0xc0 arch/x86/mm/fault.c:1484 asm_exc_page_fault+0x1e/0x30 arch/x86/include/asm/idtentry.h:571 page last free stack trace: reset_page_owner include/linux/page_owner.h:28 [inline] free_pages_prepare mm/page_alloc.c:1349 [inline] free_pcp_prepare+0x1a7/0x230 mm/page_alloc.c:1421 free_unref_page_prepare mm/page_alloc.c:3336 [inline] free_unref_page_list+0x18a/0xae0 mm/page_alloc.c:3443 release_pages+0x374/0xb00 mm/swap.c:1103 free_pages_and_swap_cache+0x180/0x1e0 mm/swap_state.c:356 tlb_batch_pages_flush mm/mmu_gather.c:49 [inline] tlb_flush_mmu_free mm/mmu_gather.c:240 [inline] tlb_flush_mmu mm/mmu_gather.c:247 [inline] tlb_finish_mmu+0x129/0x790 mm/mmu_gather.c:326 unmap_region+0x2ee/0x400 mm/mmap.c:2811 __do_munmap+0x495/0x1000 mm/mmap.c:3041 __vm_munmap+0xfb/0x1a0 mm/mmap.c:3094 __do_sys_munmap mm/mmap.c:3120 [inline] __se_sys_munmap mm/mmap.c:3116 [inline] __x64_sys_munmap+0x62/0x80 mm/mmap.c:3116 do_syscall_64+0x32/0x50 arch/x86/entry/common.c:46 entry_SYSCALL_64_after_hwframe+0x61/0xcb Memory state around the buggy address: ffff8881289c4580: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff8881289c4600: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >ffff8881289c4680: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ^ ffff8881289c4700: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff8881289c4780: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ================================================================== EXT4-fs error (device loop5): ext4_read_inline_dir:1603: inode #12: block 7: comm syz-executor: path /0/file1/file0: bad entry in directory: rec_len % 4 != 0 - offset=24, inode=2239623941, rec_len=29527, size=148 fake=0 EXT4-fs error (device loop5): ext4_read_inline_dir:1603: inode #12: block 7: comm syz-executor: path /0/file1/file0: bad entry in directory: rec_len % 4 != 0 - offset=24, inode=2239623941, rec_len=29527, size=148 fake=0 EXT4-fs error (device loop5): empty_inline_dir:1856: inode #12: block 7: comm syz-executor: bad entry in directory: rec_len % 4 != 0 - offset=4, inode=2239623941, rec_len=29527, size=60 fake=0 EXT4-fs warning (device loop5): empty_inline_dir:1859: bad inline directory (dir #12) - inode 2239623941, rec_len 29527, name_len 58inline size 60 EXT4-fs error (device loop5): ext4_read_inline_dir:1603: inode #12: block 7: comm syz-executor: path /0/file1/file0: bad entry in directory: rec_len % 4 != 0 - offset=24, inode=2239623941, rec_len=29527, size=148 fake=0 EXT4-fs error (device loop5): ext4_read_inline_dir:1603: inode #12: block 7: comm syz-executor: path /0/file1/file0: bad entry in directory: rec_len % 4 != 0 - offset=24, inode=2239623941, rec_len=29527, size=148 fake=0 EXT4-fs error (device loop5): empty_inline_dir:1856: inode #12: block 7: comm syz-executor: bad entry in directory: rec_len % 4 != 0 - offset=4, inode=2239623941, rec_len=29527, size=60 fake=0 EXT4-fs warning (device loop5): empty_inline_dir:1859: bad inline directory (dir #12) - inode 2239623941, rec_len 29527, name_len 58inline size 60 EXT4-fs error (device loop5): ext4_read_inline_dir:1603: inode #12: block 7: comm syz-executor: path /0/file1/file0: bad entry in directory: rec_len % 4 != 0 - offset=24, inode=2239623941, rec_len=29527, size=148 fake=0 EXT4-fs error (device loop5): ext4_read_inline_dir:1603: inode #12: block 7: comm syz-executor: path /0/file1/file0: bad entry in directory: rec_len % 4 != 0 - offset=24, inode=2239623941, rec_len=29527, size=148 fake=0 EXT4-fs warning (device loop5): empty_inline_dir:1859: bad inline directory (dir #12) - inode 2239623941, rec_len 29527, name_len 58inline size 60 EXT4-fs warning (device loop5): empty_inline_dir:1859: bad inline directory (dir #12) - inode 2239623941, rec_len 29527, name_len 58inline size 60 EXT4-fs warning (device loop5): empty_inline_dir:1859: bad inline directory (dir #12) - inode 2239623941, rec_len 29527, name_len 58inline size 60 EXT4-fs warning (device loop5): empty_inline_dir:1859: bad inline directory (dir #12) - inode 2239623941, rec_len 29527, name_len 58inline size 60 EXT4-fs warning (device loop5): empty_inline_dir:1859: bad inline directory (dir #12) - inode 2239623941, rec_len 29527, name_len 58inline size 60 EXT4-fs warning (device loop5): empty_inline_dir:1859: bad inline directory (dir #12) - inode 2239623941, rec_len 29527, name_len 58inline size 60 EXT4-fs warning (device loop5): empty_inline_dir:1859: bad inline directory (dir #12) - inode 2239623941, rec_len 29527, name_len 58inline size 60 EXT4-fs warning (device loop5): empty_inline_dir:1859: bad inline directory (dir #12) - inode 2239623941, rec_len 29527, name_len 58inline size 60