ci2 starts bisection 2025-09-02 20:10:59.095139883 +0000 UTC m=+25583.506735619 bisecting fixing commit since 19092c8155b4f95eb4fe2e5afa22fd32307ed69b building syzkaller on f3558dbf032eab2b77c1cb11b9ce2baffe7838d3 ensuring issue is reproducible on original commit 19092c8155b4f95eb4fe2e5afa22fd32307ed69b testing commit 19092c8155b4f95eb4fe2e5afa22fd32307ed69b gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: 20a7f371e9cce7521d42d6488d89b2d4f649d8378ccbb370d6d6b4b35fbf4cb4 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: use-after-free Read in ext4_read_inline_data run #4: crashed: KASAN: out-of-bounds 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 run #10: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #11: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #12: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #13: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #14: crashed: KASAN: use-after-free 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: use-after-free Read in ext4_read_inline_data run #18: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #19: 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] check whether we can drop unnecessary instrumentation disabling configs for [locking atomic_sleep hang memleak ubsan bug_or_warning], they are not needed testing commit 19092c8155b4f95eb4fe2e5afa22fd32307ed69b gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: 1729d375fbdc65a8db825f44d0653a88112f9558ed15ab1a01707560c0d3d782 all runs: 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 bug reproduces without the instrumentation disabling configs for [locking atomic_sleep hang memleak ubsan bug_or_warning], they are not needed kconfig minimization: base=4921 full=6215 leaves diff=255 split chunks (needed=false): <255> split chunk #0 of len 255 into 5 parts testing without sub-chunk 1/5 disabling configs for [memleak ubsan bug_or_warning locking atomic_sleep hang], they are not needed testing commit 19092c8155b4f95eb4fe2e5afa22fd32307ed69b gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: 5e5400342b42311d50836435de42f26049024f7310396320d67196ee99e43b95 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: use-after-free Read in ext4_read_inline_data run #4: crashed: KASAN: out-of-bounds 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 2/5 disabling configs for [atomic_sleep hang memleak ubsan bug_or_warning locking], they are not needed testing commit 19092c8155b4f95eb4fe2e5afa22fd32307ed69b gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: a279aa90dca2567ae41b3b647257c0340cf47a1513e6d2a9e59e985cf55a49a1 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: 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] the chunk can be dropped testing without sub-chunk 3/5 disabling configs for [atomic_sleep hang memleak ubsan bug_or_warning locking], they are not needed testing commit 19092c8155b4f95eb4fe2e5afa22fd32307ed69b gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: fd0654090e0bc9aaee23db3f0899575ff7b04cbb6820510f2b4d68473ee26f03 all runs: 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 [locking atomic_sleep hang memleak ubsan bug_or_warning], they are not needed testing commit 19092c8155b4f95eb4fe2e5afa22fd32307ed69b gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: eacb8a798b02bdd6db2b68009cb92a94689658e01ac51a7b4920f75d087e6429 all runs: 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 [atomic_sleep hang memleak ubsan bug_or_warning locking], they are not needed testing commit 19092c8155b4f95eb4fe2e5afa22fd32307ed69b gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.40 failed building 19092c8155b4f95eb4fe2e5afa22fd32307ed69b: net/socket.c:1191: undefined reference to `wext_handle_ioctl' net/socket.c:3390: undefined reference to `compat_wext_handle_ioctl' net/core/net-procfs.c:343: undefined reference to `wext_proc_exit' net/core/net-procfs.c:327: undefined reference to `wext_proc_init' minimized to 51 configs; suspects: [HID_ZEROPLUS USB_MON USB_NET_CDC_MBIM USB_NET_CDC_SUBSET USB_NET_CDC_SUBSET_ENABLE USB_NET_DM9601 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 X86_X32 ZEROPLUS_FF] disabling configs for [atomic_sleep hang memleak ubsan bug_or_warning locking], they are not needed testing current HEAD da3dbfdd15be0f7780f9c4807c7bf5429d52f201 testing commit da3dbfdd15be0f7780f9c4807c7bf5429d52f201 gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: 5e7b8d5d3d01c1e7f52323bfb67d62492d8dfded03db2e015e0fdde831835bd3 all runs: 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] crash still not fixed/happens on the oldest tested release revisions tested: 7, total time: 2h0m37.012995375s (build: 1h19m13.882998294s, test: 39m0.662223934s) crash still not fixed or there were kernel test errors commit msg: Merge android13-5.15 into android13-5.15-lts crash: KASAN: use-after-free Read in ext4_read_inline_data ================================================================== BUG: KASAN: use-after-free in ext4_read_inline_data fs/ext4/inline.c:210 [inline] BUG: KASAN: use-after-free in ext4_read_inline_data+0x1f3/0x2d0 fs/ext4/inline.c:178 Read of size 68 at addr ffff888128a51d05 by task syz-executor/491 CPU: 0 PID: 491 Comm: syz-executor Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x38/0x49 lib/dump_stack.c:106 print_address_description.constprop.0+0x24/0x160 mm/kasan/report.c:248 __kasan_report mm/kasan/report.c:427 [inline] kasan_report.cold+0x82/0xdb mm/kasan/report.c:444 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:210 [inline] ext4_read_inline_data+0x1f3/0x2d0 fs/ext4/inline.c:178 ext4_read_inline_dir+0x25c/0xda0 fs/ext4/inline.c:1533 ext4_readdir+0x3bb/0x33d0 fs/ext4/dir.c:161 iterate_dir+0x498/0x730 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 x64_sys_call+0x3fc/0x990 arch/x86/include/generated/asm/syscalls_64.h:218 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x33/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 RIP: 0033:0x7fca56150693 Code: c1 66 0f 1f 44 00 00 48 83 c4 08 48 89 ef 5b 5d e9 82 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:00007ffcc00c30b8 EFLAGS: 00000293 ORIG_RAX: 00000000000000d9 RAX: ffffffffffffffda RBX: 0000555564047520 RCX: 00007fca56150693 RDX: 0000000000008000 RSI: 0000555564047520 RDI: 0000000000000006 RBP: 00005555640474f4 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000001000 R11: 0000000000000293 R12: ffffffffffffffa8 R13: 0000000000000016 R14: 00005555640474f0 R15: 0000000000000001 The buggy address belongs to the page: page:ffffea0004a29440 refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x128a51 flags: 0x4000000000000000(zone=1) raw: 4000000000000000 ffffea0004a29488 ffffea0004a29408 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 0x100cca(GFP_HIGHUSER_MOVABLE), pid 306, ts 31505375648, free_ts 33680292817 set_page_owner include/linux/page_owner.h:33 [inline] post_alloc_hook mm/page_alloc.c:2605 [inline] prep_new_page+0x1a2/0x310 mm/page_alloc.c:2611 get_page_from_freelist+0x1ce2/0x30a0 mm/page_alloc.c:4485 __alloc_pages+0x300/0x2c90 mm/page_alloc.c:5795 __alloc_pages_node include/linux/gfp.h:595 [inline] alloc_pages_node include/linux/gfp.h:609 [inline] alloc_pages include/linux/gfp.h:622 [inline] do_cow_fault mm/memory.c:4581 [inline] do_fault mm/memory.c:4699 [inline] handle_pte_fault+0xadd/0x30a0 mm/memory.c:4911 __handle_mm_fault+0x4ea/0x1480 mm/memory.c:5207 do_handle_mm_fault+0x33b/0x690 mm/memory.c:5333 handle_mm_fault include/linux/mm.h:1836 [inline] do_user_addr_fault+0x2ea/0x1120 arch/x86/mm/fault.c:1418 handle_page_fault arch/x86/mm/fault.c:1509 [inline] exc_page_fault+0x5c/0xc0 arch/x86/mm/fault.c:1565 asm_exc_page_fault+0x27/0x30 arch/x86/include/asm/idtentry.h:606 page last free stack trace: reset_page_owner include/linux/page_owner.h:26 [inline] free_pages_prepare mm/page_alloc.c:1472 [inline] free_pcp_prepare+0x1b6/0x4c0 mm/page_alloc.c:1544 free_unref_page_prepare mm/page_alloc.c:3534 [inline] free_unref_page_list+0x1e3/0xcd0 mm/page_alloc.c:3671 release_pages+0x37f/0xff0 mm/swap.c:1014 free_pages_and_swap_cache+0x5d/0x80 mm/swap_state.c:320 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:338 exit_mmap+0x221/0x840 mm/mmap.c:3244 __mmput+0x70/0x3a0 kernel/fork.c:1180 mmput kernel/fork.c:1203 [inline] mmput+0x35/0xf0 kernel/fork.c:1197 exit_mm kernel/exit.c:554 [inline] do_exit+0x891/0x24b0 kernel/exit.c:876 do_group_exit+0xe6/0x290 kernel/exit.c:1003 get_signal+0x236/0x1e10 kernel/signal.c:2907 arch_do_signal_or_restart+0x2b4/0x21c0 arch/x86/kernel/signal.c:867 handle_signal_work kernel/entry/common.c:154 [inline] exit_to_user_mode_loop kernel/entry/common.c:178 [inline] exit_to_user_mode_prepare+0x102/0x150 kernel/entry/common.c:214 __syscall_exit_to_user_mode_work kernel/entry/common.c:296 [inline] syscall_exit_to_user_mode+0x21/0x40 kernel/entry/common.c:307 do_syscall_64+0x40/0xb0 arch/x86/entry/common.c:86 entry_SYSCALL_64_after_hwframe+0x66/0xd0 Memory state around the buggy address: ffff888128a51c00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff888128a51c80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >ffff888128a51d00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ^ ffff888128a51d80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff888128a51e00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ================================================================== EXT4-fs error (device loop4): ext4_read_inline_dir:1613: inode #12: block 5: comm syz-executor: path /0/file0/file0: bad entry in directory: rec_len % 4 != 0 - offset=24, inode=1633771873, rec_len=24929, size=148 fake=0 EXT4-fs error (device loop4): ext4_read_inline_dir:1613: inode #12: block 5: comm syz-executor: path /0/file0/file0: bad entry in directory: rec_len % 4 != 0 - offset=24, inode=1633771873, rec_len=24929, size=148 fake=0 EXT4-fs error (device loop4): empty_inline_dir:1867: inode #12: block 5: comm syz-executor: bad entry in directory: rec_len % 4 != 0 - offset=4, inode=1633771873, rec_len=24929, size=60 fake=0 EXT4-fs warning (device loop4): empty_inline_dir:1870: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60 EXT4-fs error (device loop4): ext4_read_inline_dir:1613: inode #12: block 5: comm syz-executor: path /0/file0/file0: bad entry in directory: rec_len % 4 != 0 - offset=24, inode=1633771873, rec_len=24929, size=148 fake=0 EXT4-fs error (device loop4): ext4_read_inline_dir:1613: inode #12: block 5: comm syz-executor: path /0/file0/file0: bad entry in directory: rec_len % 4 != 0 - offset=24, inode=1633771873, rec_len=24929, size=148 fake=0 EXT4-fs error (device loop4): empty_inline_dir:1867: inode #12: block 5: comm syz-executor: bad entry in directory: rec_len % 4 != 0 - offset=4, inode=1633771873, rec_len=24929, size=60 fake=0 EXT4-fs warning (device loop4): empty_inline_dir:1870: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60 EXT4-fs error (device loop4): ext4_read_inline_dir:1613: inode #12: block 5: comm syz-executor: path /0/file0/file0: bad entry in directory: rec_len % 4 != 0 - offset=24, inode=1633771873, rec_len=24929, size=148 fake=0 EXT4-fs error (device loop4): ext4_read_inline_dir:1613: inode #12: block 5: comm syz-executor: path /0/file0/file0: bad entry in directory: rec_len % 4 != 0 - offset=24, inode=1633771873, rec_len=24929, size=148 fake=0 EXT4-fs error (device loop4): empty_inline_dir:1867: inode #12: block 5: comm syz-executor: bad entry in directory: rec_len % 4 != 0 - offset=4, inode=1633771873, rec_len=24929, size=60 fake=0 EXT4-fs warning (device loop4): empty_inline_dir:1870: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60 EXT4-fs warning (device loop4): empty_inline_dir:1870: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60 EXT4-fs warning (device loop4): empty_inline_dir:1870: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60 EXT4-fs warning (device loop4): empty_inline_dir:1870: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60 EXT4-fs warning (device loop4): empty_inline_dir:1870: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60 EXT4-fs warning (device loop4): empty_inline_dir:1870: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60 EXT4-fs warning (device loop4): empty_inline_dir:1870: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60 EXT4-fs warning (device loop4): empty_inline_dir:1870: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60