ci2 starts bisection 2025-08-25 17:50:13.481999551 +0000 UTC m=+311163.245162582 bisecting fixing commit since e2b9748880b939d8d99877b72cc4cc42951d49b6 building syzkaller on d3ccff6372e07c6aabd02b5da419aa6492b5f0ad ensuring issue is reproducible on original commit e2b9748880b939d8d99877b72cc4cc42951d49b6 testing commit e2b9748880b939d8d99877b72cc4cc42951d49b6 gcc compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7 kernel signature: fd27a35871144646b372ef79dc40d5a018c8a94070756ae4f40bdf92bf4b914e run #0: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #1: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #2: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #3: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #4: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #5: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #6: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #7: crashed: KASAN: out-of-bounds Read in ext4_read_inline_dir run #8: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #9: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #10: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #11: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #12: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #13: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #14: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #15: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #16: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #17: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #18: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #19: crashed: KASAN: use-after-free Read in ext4_read_inline_dir representative crash: KASAN: use-after-free Read in ext4_read_inline_dir, types: [KASAN-USE-AFTER-FREE-READ] check whether we can drop unnecessary instrumentation disabling configs for [memleak ubsan bug_or_warning locking atomic_sleep hang], they are not needed testing commit e2b9748880b939d8d99877b72cc4cc42951d49b6 gcc compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7 kernel signature: d60378a349ad8e201da9dd943c3f3cb32f54234b2b08da579dd908b53bb9ac7e all runs: crashed: KASAN: use-after-free Read in ext4_read_inline_dir representative crash: KASAN: use-after-free Read in ext4_read_inline_dir, 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=5186 full=6548 leaves diff=266 split chunks (needed=false): <266> split chunk #0 of len 266 into 5 parts testing without sub-chunk 1/5 disabling configs for [ubsan bug_or_warning locking atomic_sleep hang memleak], they are not needed testing commit e2b9748880b939d8d99877b72cc4cc42951d49b6 gcc compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7 kernel signature: 39e91a8b6b358342c1dc63a5dac48f11335d223f182ac41d6fcdeb8fab3d3f85 all runs: crashed: KASAN: use-after-free Read in ext4_read_inline_dir representative crash: KASAN: use-after-free Read in ext4_read_inline_dir, types: [KASAN-USE-AFTER-FREE-READ] the chunk can be dropped testing without sub-chunk 2/5 disabling configs for [memleak ubsan bug_or_warning locking atomic_sleep hang], they are not needed testing commit e2b9748880b939d8d99877b72cc4cc42951d49b6 gcc compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7 kernel signature: c29003cf0615f8059d5537af9b5d0e7c7e9b3096976c63ac4d3e3dc248b8a37b all runs: crashed: KASAN: use-after-free Read in ext4_read_inline_dir representative crash: KASAN: use-after-free Read in ext4_read_inline_dir, types: [KASAN-USE-AFTER-FREE-READ] the chunk can be dropped testing without sub-chunk 3/5 disabling configs for [ubsan bug_or_warning locking atomic_sleep hang memleak], they are not needed testing commit e2b9748880b939d8d99877b72cc4cc42951d49b6 gcc compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7 kernel signature: 5347c35258a042ff3ff41a9aadd3db3c4e781926310e163048811666cd0525b5 run #0: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #1: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #2: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #3: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #4: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_dir run #5: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #6: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #7: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #8: crashed: KASAN: out-of-bounds Read in ext4_read_inline_dir run #9: crashed: KASAN: use-after-free Read in ext4_read_inline_dir representative crash: KASAN: use-after-free Read in ext4_read_inline_dir, types: [KASAN-USE-AFTER-FREE-READ] the chunk can be dropped testing without sub-chunk 4/5 disabling configs for [atomic_sleep hang memleak ubsan bug_or_warning locking], they are not needed testing commit e2b9748880b939d8d99877b72cc4cc42951d49b6 gcc compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7 kernel signature: edcf08f6edac692706154c47e3e719478d96d554ad7d491f419fe0cdd0be7a25 all runs: crashed: KASAN: use-after-free Read in ext4_read_inline_dir representative crash: KASAN: use-after-free Read in ext4_read_inline_dir, types: [KASAN-USE-AFTER-FREE-READ] the chunk can be dropped testing without sub-chunk 5/5 disabling configs for [memleak ubsan bug_or_warning locking atomic_sleep hang], they are not needed testing commit e2b9748880b939d8d99877b72cc4cc42951d49b6 gcc compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7 failed building e2b9748880b939d8d99877b72cc4cc42951d49b6: ld.lld: error: undefined symbol: wext_proc_init ld.lld: error: undefined symbol: wext_proc_exit ld.lld: error: undefined symbol: wext_handle_ioctl ld.lld: error: undefined symbol: compat_wext_handle_ioctl minimized to 50 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_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 V4L2_ASYNC V4L2_FWNODE VIDEO_CAMERA_SENSOR WLAN WLAN_VENDOR_ATH WLAN_VENDOR_ATMEL WLAN_VENDOR_BROADCOM WLAN_VENDOR_INTERSIL WLAN_VENDOR_MARVELL WLAN_VENDOR_MEDIATEK WLAN_VENDOR_MICROCHIP WLAN_VENDOR_PURELIFI WLAN_VENDOR_RALINK WLAN_VENDOR_REALTEK WLAN_VENDOR_RSI WLAN_VENDOR_SILABS WLAN_VENDOR_ZYDAS X86_X32_ABI ZEROPLUS_FF] disabling configs for [ubsan bug_or_warning locking atomic_sleep hang memleak], they are not needed testing current HEAD 47b374a18638c5f0aa6d3cf4f5026f172aa767b3 testing commit 47b374a18638c5f0aa6d3cf4f5026f172aa767b3 gcc compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7 kernel signature: 22cd8b7475cde0f111c8a13f7988e59b28b36f369c8b5681381437bad8280a4e run #0: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #1: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #2: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #3: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #4: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #5: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #6: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #7: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #8: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #9: ignore: lost connection to test machine representative crash: KASAN: use-after-free Read in ext4_read_inline_dir, types: [KASAN-USE-AFTER-FREE-READ] crash still not fixed/happens on the oldest tested release revisions tested: 7, total time: 2h41m52.950996223s (build: 1h25m32.450886268s, test: 44m2.776275381s) crash still not fixed or there were kernel test errors commit msg: BACKPORT: FROMGIT: f2fs: add sysfs entry for effective lookup mode crash: KASAN: use-after-free Read in ext4_read_inline_dir ================================================================== 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_dir+0x344/0xbe0 fs/ext4/inline.c:1512 Read of size 68 at addr ffff88812a672d05 by task syz-executor/489 CPU: 1 PID: 489 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+0x19/0x1c lib/dump_stack.c:88 dump_stack_lvl+0xa3/0xec lib/dump_stack.c:106 print_address_description+0x71/0x210 mm/kasan/report.c:316 print_report+0x4a/0x60 mm/kasan/report.c:427 kasan_report+0x122/0x150 mm/kasan/report.c:531 check_region_inline mm/kasan/generic.c:-1 [inline] kasan_check_range+0x280/0x290 mm/kasan/generic.c:189 memcpy+0x2d/0x70 mm/kasan/shadow.c:65 ext4_read_inline_data fs/ext4/inline.c:210 [inline] ext4_read_inline_dir+0x344/0xbe0 fs/ext4/inline.c:1512 ext4_readdir+0x256/0x31e0 fs/ext4/dir.c:161 iterate_dir+0x221/0x540 fs/readdir.c:-1 __do_sys_getdents64 fs/readdir.c:369 [inline] __se_sys_getdents64+0xc9/0x190 fs/readdir.c:354 __x64_sys_getdents64+0x76/0x80 fs/readdir.c:354 x64_sys_call+0x15c/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:218 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x68/0xd2 RIP: 0033:0x7f3324db8693 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:00007ffe29059618 EFLAGS: 00000293 ORIG_RAX: 00000000000000d9 RAX: ffffffffffffffda RBX: 0000555589616520 RCX: 00007f3324db8693 RDX: 0000000000008000 RSI: 0000555589616520 RDI: 0000000000000006 RBP: 00005555896164f4 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000001000 R11: 0000000000000293 R12: ffffffffffffffa8 R13: 0000000000000016 R14: 00005555896164f0 R15: 0000000000000001 The buggy address belongs to the physical page: page:ffffea0004a99c80 refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x12a672 flags: 0x4000000000000000(zone=1) raw: 4000000000000000 ffffea0004a99cc8 ffffea0004a99c48 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 0x8140dca(GFP_HIGHUSER_MOVABLE|__GFP_COMP|__GFP_ZERO|__GFP_CMA), pid 309, tgid 305 (syz-execprog), ts 33873034443, free_ts 34911731076 set_page_owner include/linux/page_owner.h:33 [inline] post_alloc_hook mm/page_alloc.c:2637 [inline] prep_new_page+0x58c/0x650 mm/page_alloc.c:2644 get_page_from_freelist+0x2f0f/0x2f80 mm/page_alloc.c:4544 __alloc_pages+0x1c3/0x450 mm/page_alloc.c:5858 __folio_alloc+0x12/0x40 mm/page_alloc.c:5890 __folio_alloc_node include/linux/gfp.h:245 [inline] folio_alloc include/linux/gfp.h:274 [inline] alloc_page_vma include/linux/gfp.h:283 [inline] do_anonymous_page mm/memory.c:4283 [inline] handle_pte_fault mm/memory.c:5169 [inline] __handle_mm_fault mm/memory.c:5313 [inline] handle_mm_fault+0x1006/0x1a80 mm/memory.c:5453 do_user_addr_fault+0x5f8/0xa10 arch/x86/mm/fault.c:1323 handle_page_fault arch/x86/mm/fault.c:1466 [inline] exc_page_fault+0x51/0xb0 arch/x86/mm/fault.c:1522 asm_exc_page_fault+0x27/0x30 arch/x86/include/asm/idtentry.h:608 page last free stack trace: reset_page_owner include/linux/page_owner.h:26 [inline] free_pages_prepare mm/page_alloc.c:1545 [inline] free_pcp_prepare mm/page_alloc.c:1619 [inline] free_unref_page_prepare+0x645/0x650 mm/page_alloc.c:3581 free_unref_page_list+0x112/0x890 mm/page_alloc.c:3730 release_pages+0x904/0x960 mm/swap.c:1043 free_pages_and_swap_cache+0x66/0x80 mm/swap_state.c:315 tlb_batch_pages_flush mm/mmu_gather.c:59 [inline] tlb_flush_mmu_free mm/mmu_gather.c:254 [inline] tlb_flush_mmu+0xf1/0x1b0 mm/mmu_gather.c:261 zap_pte_range mm/memory.c:1547 [inline] zap_pmd_range mm/memory.c:1596 [inline] zap_pud_range mm/memory.c:1625 [inline] zap_p4d_range mm/memory.c:1646 [inline] unmap_page_range+0x79c/0x17b0 mm/memory.c:1667 unmap_single_vma mm/memory.c:1713 [inline] unmap_vmas+0x29d/0x380 mm/memory.c:1753 exit_mmap+0x213/0x7e0 mm/mmap.c:3354 __mmput+0x6b/0x2a0 kernel/fork.c:1297 mmput+0x2a/0xe0 kernel/fork.c:1320 exit_mm kernel/exit.c:568 [inline] do_exit+0x7b5/0x1fe0 kernel/exit.c:873 do_group_exit+0x1a1/0x280 kernel/exit.c:1028 get_signal+0xeb4/0xfc0 kernel/signal.c:2889 arch_do_signal_or_restart+0xb0/0x1030 arch/x86/kernel/signal.c:871 exit_to_user_mode_loop+0x7a/0xb0 kernel/entry/common.c:174 exit_to_user_mode_prepare+0x5a/0xa0 kernel/entry/common.c:210 Memory state around the buggy address: ffff88812a672c00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff88812a672c80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >ffff88812a672d00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ^ ffff88812a672d80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff88812a672e00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ================================================================== EXT4-fs error (device loop0): ext4_read_inline_dir:1593: 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 loop0): ext4_read_inline_dir:1593: 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 loop0): empty_inline_dir:1877: 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 loop0): empty_inline_dir:1884: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60 EXT4-fs error (device loop0): ext4_read_inline_dir:1593: 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 loop0): ext4_read_inline_dir:1593: 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 loop0): empty_inline_dir:1877: 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 loop0): empty_inline_dir:1884: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60 EXT4-fs error (device loop0): ext4_read_inline_dir:1593: 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 loop0): ext4_read_inline_dir:1593: 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 loop0): empty_inline_dir:1877: 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 loop0): empty_inline_dir:1884: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60 EXT4-fs warning (device loop0): empty_inline_dir:1884: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60 EXT4-fs warning (device loop0): empty_inline_dir:1884: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60 EXT4-fs warning (device loop0): empty_inline_dir:1884: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60 EXT4-fs warning (device loop0): empty_inline_dir:1884: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60 EXT4-fs warning (device loop0): empty_inline_dir:1884: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60 EXT4-fs warning (device loop0): empty_inline_dir:1884: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60 EXT4-fs warning (device loop0): empty_inline_dir:1884: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60 EXT4-fs (loop0): unmounting filesystem.