ci2 starts bisection 2025-09-13 14:38:07.732412118 +0000 UTC m=+156199.607227245 bisecting fixing commit since 145c7fad733f13d7a8f4aa156785f40d38e966da building syzkaller on 7117feecc9626dc60b06fb3e91c0f7632d99d30b ensuring issue is reproducible on original commit 145c7fad733f13d7a8f4aa156785f40d38e966da testing commit 145c7fad733f13d7a8f4aa156785f40d38e966da gcc compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 kernel signature: 67b691bf67576a0a23fda3aa05292f3e3b6c8a725a735f269aa7bf7376491c11 all runs: crashed: KASAN: use-after-free Read in ext4_ext_remove_space representative crash: KASAN: use-after-free Read in ext4_ext_remove_space, types: [KASAN-USE-AFTER-FREE-READ] check whether we can drop unnecessary instrumentation disabling configs for [hang memleak ubsan bug_or_warning locking atomic_sleep], they are not needed testing commit 145c7fad733f13d7a8f4aa156785f40d38e966da gcc compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 kernel signature: 4f2825d843b98cc8feed07efdffbd8a061c123f2b78e400276a598847cc0902d all runs: crashed: KASAN: use-after-free Read in ext4_ext_remove_space representative crash: KASAN: use-after-free Read in ext4_ext_remove_space, types: [KASAN-USE-AFTER-FREE-READ] the bug reproduces without the instrumentation disabling configs for [hang memleak ubsan bug_or_warning locking atomic_sleep], 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 [ubsan bug_or_warning locking atomic_sleep hang memleak], they are not needed testing commit 145c7fad733f13d7a8f4aa156785f40d38e966da gcc compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 kernel signature: 5adb888edfbdc31ee0478e12d0d02f16c6aab3b6c9f897dc3dff2213518df341 all runs: crashed: KASAN: use-after-free Read in ext4_ext_remove_space representative crash: KASAN: use-after-free Read in ext4_ext_remove_space, types: [KASAN-USE-AFTER-FREE-READ] the chunk can be dropped testing without sub-chunk 2/5 disabling configs for [locking atomic_sleep hang memleak ubsan bug_or_warning], they are not needed testing commit 145c7fad733f13d7a8f4aa156785f40d38e966da gcc compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 kernel signature: 9bef27f6f34fa4c8e4c0b750e65d711fc579cdd6535f72d823697231687b7b58 all runs: crashed: KASAN: use-after-free Read in ext4_ext_remove_space representative crash: KASAN: use-after-free Read in ext4_ext_remove_space, types: [KASAN-USE-AFTER-FREE-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 145c7fad733f13d7a8f4aa156785f40d38e966da gcc compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 kernel signature: 8b63b35885154064f78357b5fa82c6a4f06e34c2f78a02311ded6b183226ccc2 all runs: crashed: KASAN: use-after-free Read in ext4_ext_remove_space representative crash: KASAN: use-after-free Read in ext4_ext_remove_space, 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 145c7fad733f13d7a8f4aa156785f40d38e966da gcc compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 kernel signature: 44f8267cf247752f93d4511ef70cf7a39b7df0c30ca523f561c42f3928dd6f37 all runs: crashed: KASAN: use-after-free Read in ext4_ext_remove_space representative crash: KASAN: use-after-free Read in ext4_ext_remove_space, types: [KASAN-USE-AFTER-FREE-READ] the chunk can be dropped testing without sub-chunk 5/5 disabling configs for [hang memleak ubsan bug_or_warning locking atomic_sleep], they are not needed testing commit 145c7fad733f13d7a8f4aa156785f40d38e966da gcc compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 failed building 145c7fad733f13d7a8f4aa156785f40d38e966da: 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 0429b7af308cf65c84109c08d06b01950dcd57fe testing commit 0429b7af308cf65c84109c08d06b01950dcd57fe gcc compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 kernel signature: bc7ff07d42e85761f559a88d2234e341f703931218c4fef5079fb7563b4b87fa all runs: crashed: KASAN: use-after-free Read in ext4_ext_remove_space representative crash: KASAN: use-after-free Read in ext4_ext_remove_space, types: [KASAN-USE-AFTER-FREE-READ] crash still not fixed/happens on the oldest tested release revisions tested: 7, total time: 1h52m19.402641222s (build: 47m5.536718803s, test: 1h1m3.616980996s) crash still not fixed or there were kernel test errors commit msg: ANDROID: KVM: arm64: Fix CPU type when reading trace_pdesc crash: KASAN: use-after-free Read in ext4_ext_remove_space ================================================================== BUG: KASAN: use-after-free in ext4_ext_rm_leaf fs/ext4/extents.c:2602 [inline] BUG: KASAN: use-after-free in ext4_ext_remove_space+0x2fa3/0x3ed0 fs/ext4/extents.c:2940 Read of size 4 at addr ffff888129c89db8 by task syz-executor/435 CPU: 0 PID: 435 Comm: syz-executor Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/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/0x1e0 mm/kasan/report.c:316 print_report+0x4a/0x60 mm/kasan/report.c:418 kasan_report+0x122/0x150 mm/kasan/report.c:522 __asan_report_load4_noabort+0x14/0x20 mm/kasan/report_generic.c:350 ext4_ext_rm_leaf fs/ext4/extents.c:2602 [inline] ext4_ext_remove_space+0x2fa3/0x3ed0 fs/ext4/extents.c:2940 ext4_ext_truncate+0x195/0x270 fs/ext4/extents.c:4470 ext4_truncate+0xa23/0xe20 fs/ext4/inode.c:4291 ext4_evict_inode+0xc87/0x12a0 fs/ext4/inode.c:286 evict+0x3eb/0x820 fs/inode.c:705 iput_final fs/inode.c:1834 [inline] iput+0x4c1/0x4f0 fs/inode.c:1860 do_unlinkat+0x36a/0x5d0 fs/namei.c:4396 __do_sys_unlink fs/namei.c:4437 [inline] __se_sys_unlink fs/namei.c:4435 [inline] __x64_sys_unlink+0x44/0x50 fs/namei.c:4435 x64_sys_call+0x958/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:88 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:0x7ff2fc58df57 Code: 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 57 00 00 00 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:00007fffe77c08c8 EFLAGS: 00000206 ORIG_RAX: 0000000000000057 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007ff2fc58df57 RDX: 00007fffe77c08f0 RSI: 00007fffe77c0980 RDI: 00007fffe77c0980 RBP: 00007fffe77c0980 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000100 R11: 0000000000000206 R12: 00007fffe77c1a70 R13: 00007ff2fc610b55 R14: 000000000000e96b R15: 00007fffe77c2b40 The buggy address belongs to the physical page: page:ffffea0004a72240 refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x129c89 flags: 0x4000000000000000(zone=1) raw: 4000000000000000 ffffea0004968c88 ffffea0004a72208 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 431, tgid 431 (syz-executor), ts 58792530024, free_ts 58898074959 set_page_owner include/linux/page_owner.h:33 [inline] post_alloc_hook mm/page_alloc.c:2643 [inline] prep_new_page+0x58c/0x650 mm/page_alloc.c:2650 get_page_from_freelist+0x2f0f/0x2f80 mm/page_alloc.c:4554 __alloc_pages+0x1c3/0x450 mm/page_alloc.c:5868 __folio_alloc+0x12/0x40 mm/page_alloc.c:5900 __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] wp_page_copy+0x21d/0x10e0 mm/memory.c:3210 do_wp_page+0x9ef/0xc70 mm/memory.c:-1 handle_pte_fault mm/memory.c:5189 [inline] __handle_mm_fault mm/memory.c:5313 [inline] handle_mm_fault+0xac6/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:1551 [inline] free_pcp_prepare mm/page_alloc.c:1625 [inline] free_unref_page_prepare+0x645/0x650 mm/page_alloc.c:3589 free_unref_page_list+0x112/0x890 mm/page_alloc.c:3740 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+0x333/0x8c0 mm/mmap.c:3378 __mmput+0x6b/0x2a0 kernel/fork.c:1300 mmput+0x2a/0xe0 kernel/fork.c:1323 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: ffff888129c89c80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff888129c89d00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >ffff888129c89d80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ^ ffff888129c89e00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff888129c89e80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ================================================================== EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 0, count = 0 EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 0, count = 16 EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 263066746924816, count = 16 EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 263066746912628, count = 12201 EXT4-fs (loop2): unmounting filesystem. EXT4-fs (loop2): unmounting filesystem. EXT4-fs (loop2): unmounting filesystem. EXT4-fs (loop2): unmounting filesystem. EXT4-fs (loop2): unmounting filesystem. EXT4-fs (loop2): unmounting filesystem. EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 281466437271280, count = 16 EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 281466437239040, count = 32252 EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 281466437239040, count = 16 EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 268224867821536, count = 16 EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 268224867792372, count = 29168 EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 268224867792368, count = 16 EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 254978986561472, count = 16 EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 254978986535400, count = 26084 EXT4-fs (loop2): unmounting filesystem. EXT4-fs (loop2): unmounting filesystem. EXT4-fs (loop2): unmounting filesystem. EXT4-fs (loop2): unmounting filesystem. EXT4-fs (loop2): unmounting filesystem. EXT4-fs (loop2): unmounting filesystem. EXT4-fs (loop2): unmounting filesystem. EXT4-fs (loop2): unmounting filesystem. EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 154289888, count = 16 EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 154257264, count = 32639 EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 10106058098400, count = 16 EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 10106058080127, count = 18288 EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 10106058080112, count = 16 EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 154289888, count = 16 EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 154257264, count = 32639 EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 10106058098400, count = 16 EXT4-fs (loop2): unmounting filesystem. EXT4-fs (loop2): unmounting filesystem. EXT4-fs (loop2): unmounting filesystem. EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 54117547481232, count = 16 EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 54117547455029, count = 26214 EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 54117547455024, count = 16 EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 129078370140112, count = 16 EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 129078370110053, count = 30065 EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 129078370110048, count = 16 EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 109261609361856, count = 16 EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 109261609331810, count = 30051 EXT4-fs error: 39571 callbacks suppressed EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 35392130588752, count = 16 EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 112589218958528, count = 16 EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 112589218932326, count = 26214 EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 112589218932320, count = 16 EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 109261526393568, count = 16 EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 109261526364008, count = 29561 EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 109261526364000, count = 16 EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 104906210526656, count = 16 EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 104906210500447, count = 26211 EXT4-fs error (device loop2): ext4_free_blocks:6210: comm syz-executor: Freeing blocks not in datazone - block = 104906210500432, count = 16