ci2 starts bisection 2025-07-27 20:46:07.776467992 +0000 UTC m=+251385.481929058 bisecting fixing commit since 47e5d7e917782dd01d2ddb37de9a37b33ab19a6c building syzkaller on 5d7e17caf7d0971d22446d8a81bcf1cd8c18a0dc ensuring issue is reproducible on original commit 47e5d7e917782dd01d2ddb37de9a37b33ab19a6c testing commit 47e5d7e917782dd01d2ddb37de9a37b33ab19a6c gcc compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7 kernel signature: 5541106d9f222f87d6efac837e52344b7c54c8141e6fe21a339bb42262a94e81 all runs: crashed: KASAN: use-after-free Read in __ext4_check_dir_entry representative crash: KASAN: use-after-free Read in __ext4_check_dir_entry, 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 47e5d7e917782dd01d2ddb37de9a37b33ab19a6c gcc compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7 kernel signature: e0ed8e69ef984db5b91ee5e225058d4fc71a7a5df4126606319dd2945bbc23a4 all runs: crashed: KASAN: use-after-free Read in __ext4_check_dir_entry representative crash: KASAN: use-after-free Read in __ext4_check_dir_entry, 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=6555 leaves diff=264 split chunks (needed=false): <264> split chunk #0 of len 264 into 5 parts testing without sub-chunk 1/5 disabling configs for [locking atomic_sleep hang memleak ubsan bug_or_warning], they are not needed testing commit 47e5d7e917782dd01d2ddb37de9a37b33ab19a6c gcc compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7 kernel signature: 8dfda456f63aa135416bff8b9d1f550c539f98c6ff6d3c23e7a3af1df105b1d6 all runs: crashed: KASAN: use-after-free Read in __ext4_check_dir_entry representative crash: KASAN: use-after-free Read in __ext4_check_dir_entry, 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 47e5d7e917782dd01d2ddb37de9a37b33ab19a6c gcc compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7 kernel signature: 892f6e6bcf9ebb301ed8a62e75e9c981a5b8f030381b52fec6e661691dec58a9 all runs: crashed: KASAN: use-after-free Read in __ext4_check_dir_entry representative crash: KASAN: use-after-free Read in __ext4_check_dir_entry, types: [KASAN-USE-AFTER-FREE-READ] the chunk can be dropped testing without sub-chunk 3/5 disabling configs for [memleak ubsan bug_or_warning locking atomic_sleep hang], they are not needed testing commit 47e5d7e917782dd01d2ddb37de9a37b33ab19a6c gcc compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7 kernel signature: 47be53825a572ea6d0a74233fe77b010e1896446282b8c516575062ba1998609 all runs: crashed: KASAN: use-after-free Read in __ext4_check_dir_entry representative crash: KASAN: use-after-free Read in __ext4_check_dir_entry, 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 47e5d7e917782dd01d2ddb37de9a37b33ab19a6c gcc compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7 kernel signature: 45420c7e8dacb578129c14c18b8d861a8887bae401195a7e31a99de926a39a57 all runs: crashed: KASAN: use-after-free Read in __ext4_check_dir_entry representative crash: KASAN: use-after-free Read in __ext4_check_dir_entry, types: [KASAN-USE-AFTER-FREE-READ] the chunk can be dropped testing without sub-chunk 5/5 disabling configs for [locking atomic_sleep hang memleak ubsan bug_or_warning], they are not needed testing commit 47e5d7e917782dd01d2ddb37de9a37b33ab19a6c gcc compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7 failed building 47e5d7e917782dd01d2ddb37de9a37b33ab19a6c: 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 52 configs; suspects: [HID_ZEROPLUS 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_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 ZEROPLUS_FF] disabling configs for [hang memleak ubsan bug_or_warning locking atomic_sleep], they are not needed testing current HEAD 2ff414a09808fbe42a69974f69b534f6e0933ed1 testing commit 2ff414a09808fbe42a69974f69b534f6e0933ed1 gcc compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7 kernel signature: 098998e7136507e0d10859f00a88dcaea9f28246b9a69f1f30f49f6233fb30cb all runs: crashed: KASAN: use-after-free Read in __ext4_check_dir_entry representative crash: KASAN: use-after-free Read in __ext4_check_dir_entry, types: [KASAN-USE-AFTER-FREE-READ] crash still not fixed/happens on the oldest tested release revisions tested: 7, total time: 2h40m37.268711317s (build: 1h57m47.489772381s, test: 24m40.14044691s) crash still not fixed or there were kernel test errors commit msg: Merge tag 'android14-6.1.145_r00' into android14-6.1 crash: KASAN: use-after-free Read in __ext4_check_dir_entry EXT4-fs warning (device loop2): dx_probe:966: inode #2: comm syz.2.18: Corrupt directory, running e2fsck is recommended ================================================================== BUG: KASAN: use-after-free in __ext4_check_dir_entry+0x442/0x670 fs/ext4/dir.c:85 Read of size 2 at addr ffff888125724003 by task syz.2.18/457 CPU: 0 PID: 457 Comm: syz.2.18 Not tainted 6.1.145-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/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 __asan_report_load2_noabort+0x14/0x20 mm/kasan/report_generic.c:349 __ext4_check_dir_entry+0x442/0x670 fs/ext4/dir.c:85 ext4_readdir+0xbb6/0x31e0 fs/ext4/dir.c:261 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:0x7f444ed8e929 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f444fb3d038 EFLAGS: 00000246 ORIG_RAX: 00000000000000d9 RAX: ffffffffffffffda RBX: 00007f444efb5fa0 RCX: 00007f444ed8e929 RDX: 0000000000000010 RSI: 0000000000000000 RDI: 0000000000000004 RBP: 00007f444ee10b39 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007f444efb5fa0 R15: 00007ffc5aee1c38 The buggy address belongs to the physical page: page:ffffea000495c900 refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x125724 flags: 0x4000000000000000(zone=1) raw: 4000000000000000 ffffea000495c948 ffff8881f733c568 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 0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), pid 430, tgid 430 (syz-executor), ts 56337334155, free_ts 56435455749 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:4539 __alloc_pages+0x19e/0x3a0 mm/page_alloc.c:5850 __folio_alloc+0x12/0x40 mm/page_alloc.c:5882 __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_cow_fault mm/memory.c:4761 [inline] do_fault+0x6f6/0x17a0 mm/memory.c:4877 handle_pte_fault mm/memory.c:5171 [inline] __handle_mm_fault mm/memory.c:5313 [inline] handle_mm_fault+0xba9/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+0xba/0x790 mm/page_alloc.c:3729 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 mm/mmu_gather.c:261 [inline] tlb_finish_mmu+0x1af/0x380 mm/mmu_gather.c:361 exit_mmap+0x30a/0x7e0 mm/mmap.c:3367 __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 __syscall_exit_to_user_mode_work kernel/entry/common.c:292 [inline] syscall_exit_to_user_mode+0x1a/0x30 kernel/entry/common.c:303 do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:87 Memory state around the buggy address: ffff888125723f00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff888125723f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffff888125724000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ^ ffff888125724080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff888125724100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ================================================================== EXT4-fs error (device loop2): ext4_readdir:263: inode #2: block 255: comm syz.2.18: path (unknown): bad entry in directory: directory entry overrun - offset=1023, inode=1819625984, rec_len=12832, size=1024 fake=0