ci2 starts bisection 2026-08-09 15:57:45.755222444 +0000 UTC m=+129665.007827518 bisecting fixing commit since fc9aa81462ee32fea3dd6d7c6d8d7dcdb69637df building syzkaller on e28266709dd2a1d1452d4a5bbf271700e10335c6 ensuring issue is reproducible on original commit fc9aa81462ee32fea3dd6d7c6d8d7dcdb69637df testing commit fc9aa81462ee32fea3dd6d7c6d8d7dcdb69637df gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.44 kernel signature: 494954cf5f985ce9dc4565037d713afd6015914b5a9a3740f66d183bb923f66f run #0: crashed: KASAN: out-of-bounds Read in ext4_ext_insert_extent run #1: crashed: KASAN: use-after-free Write in ext4_ext_remove_space run #2: crashed: KASAN: use-after-free Read in ext4_ext_insert_extent run #3: crashed: KASAN: use-after-free Read in ext4_ext_insert_extent run #4: crashed: KASAN: use-after-free Write in ext4_ext_remove_space run #5: crashed: KASAN: use-after-free Write in ext4_ext_remove_space run #6: crashed: KASAN: use-after-free Read in ext4_ext_insert_extent run #7: crashed: KASAN: use-after-free Read in ext4_ext_insert_extent run #8: crashed: KASAN: use-after-free Write in ext4_ext_remove_space run #9: crashed: KASAN: use-after-free Read in ext4_ext_remove_space run #10: crashed: KASAN: use-after-free Write in ext4_ext_remove_space run #11: crashed: KASAN: use-after-free Write in ext4_ext_remove_space run #12: crashed: KASAN: use-after-free Write in ext4_ext_remove_space run #13: crashed: KASAN: use-after-free Write in ext4_ext_remove_space run #14: crashed: KASAN: use-after-free Read in ext4_ext_insert_extent run #15: crashed: KASAN: use-after-free Write in ext4_ext_remove_space run #16: crashed: KASAN: use-after-free Read in ext4_ext_insert_extent run #17: crashed: KASAN: use-after-free Read in ext4_ext_insert_extent run #18: crashed: KASAN: use-after-free Read in ext4_ext_insert_extent run #19: crashed: KASAN: use-after-free Read in ext4_ext_insert_extent representative crash: KASAN: use-after-free Read in ext4_ext_insert_extent, types: [KASAN-USE-AFTER-FREE-READ KASAN-USE-AFTER-FREE-WRITE] check whether we can drop unnecessary instrumentation disabling configs for [ubsan bug_or_warning locking atomic_sleep hang memleak], they are not needed testing commit fc9aa81462ee32fea3dd6d7c6d8d7dcdb69637df gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.44 kernel signature: a659e5056f4e3232c745face0365463924959547fdcf25df4a767c77da4caf4a run #0: crashed: KASAN: use-after-free Read in ext4_ext_insert_extent run #1: crashed: KASAN: use-after-free Read in ext4_ext_insert_extent run #2: crashed: KASAN: use-after-free Read in ext4_ext_insert_extent run #3: crashed: KASAN: use-after-free Write in ext4_ext_remove_space run #4: crashed: KASAN: use-after-free Write in ext4_ext_remove_space run #5: crashed: KASAN: use-after-free Write in ext4_ext_remove_space run #6: crashed: KASAN: use-after-free Read in ext4_find_extent run #7: crashed: KASAN: use-after-free Write in ext4_ext_remove_space run #8: crashed: KASAN: use-after-free Read in ext4_ext_insert_extent run #9: crashed: KASAN: use-after-free Write in ext4_ext_remove_space representative crash: KASAN: use-after-free Read in ext4_ext_insert_extent, types: [KASAN-USE-AFTER-FREE-READ KASAN-USE-AFTER-FREE-WRITE] the bug reproduces without the instrumentation disabling configs for [memleak ubsan bug_or_warning locking atomic_sleep hang], they are not needed kconfig minimization: base=4788 full=6023 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 [atomic_sleep hang memleak ubsan bug_or_warning locking], they are not needed testing commit fc9aa81462ee32fea3dd6d7c6d8d7dcdb69637df gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.44 kernel signature: 445df8d1bbe5baca2f5bacb9b9ed22db70e0cedfd217bcf6f6dd48c9725522d8 run #0: crashed: KASAN: use-after-free Write in ext4_ext_remove_space run #1: crashed: KASAN: use-after-free Read in ext4_ext_insert_extent run #2: crashed: KASAN: use-after-free Read in ext4_ext_remove_space run #3: crashed: KASAN: use-after-free Write in ext4_ext_remove_space run #4: crashed: KASAN: use-after-free Read in ext4_ext_insert_extent run #5: crashed: KASAN: use-after-free Write in ext4_ext_remove_space run #6: crashed: KASAN: use-after-free Write in ext4_ext_remove_space run #7: crashed: KASAN: out-of-bounds Write in ext4_ext_remove_space run #8: crashed: KASAN: use-after-free Read in ext4_ext_remove_space run #9: crashed: go runtime error representative crash: KASAN: use-after-free Write in ext4_ext_remove_space, types: [KASAN-USE-AFTER-FREE-WRITE 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 fc9aa81462ee32fea3dd6d7c6d8d7dcdb69637df gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.44 kernel signature: 78b952570d47574e5fc47cf7f557de6bdac5bf09d26bfecb189a1d759a7ea032 run #0: crashed: KASAN: use-after-free Read in ext4_ext_remove_space run #1: crashed: KASAN: use-after-free Read in ext4_ext_remove_space run #2: crashed: KASAN: use-after-free Read in ext4_ext_remove_space run #3: crashed: KASAN: use-after-free Write in ext4_ext_remove_space run #4: crashed: KASAN: use-after-free Read in ext4_ext_remove_space run #5: crashed: KASAN: use-after-free Read in ext4_find_extent run #6: crashed: KASAN: use-after-free Read in ext4_ext_insert_extent run #7: crashed: KASAN: use-after-free Read in ext4_ext_insert_extent run #8: crashed: KASAN: use-after-free Read in ext4_ext_remove_space run #9: crashed: KASAN: use-after-free Write 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 fc9aa81462ee32fea3dd6d7c6d8d7dcdb69637df gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.44 kernel signature: 9c971c5dcf7d2182ee543b2c7d413d7eb3091c3c7692d51b1f4b9a58518887fe run #0: crashed: KASAN: out-of-bounds Write in ext4_ext_remove_space run #1: crashed: KASAN: use-after-free Write in ext4_ext_remove_space run #2: crashed: KASAN: use-after-free Read in ext4_find_extent run #3: crashed: KASAN: use-after-free Read in ext4_find_extent run #4: crashed: KASAN: use-after-free Read in ext4_ext_insert_extent run #5: crashed: KASAN: use-after-free Read in ext4_ext_insert_extent run #6: crashed: KASAN: use-after-free Write in ext4_ext_remove_space run #7: crashed: KASAN: use-after-free Read in ext4_ext_insert_extent run #8: crashed: KASAN: use-after-free Write in ext4_ext_remove_space run #9: crashed: KASAN: use-after-free Read in ext4_ext_insert_extent representative crash: KASAN: use-after-free Read in ext4_find_extent, types: [KASAN-USE-AFTER-FREE-READ KASAN-USE-AFTER-FREE-WRITE] the chunk can be dropped testing without sub-chunk 4/5 disabling configs for [memleak ubsan bug_or_warning locking atomic_sleep hang], they are not needed testing commit fc9aa81462ee32fea3dd6d7c6d8d7dcdb69637df gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.44 kernel signature: 83872133517163e5a42d7d73aad582056aa28f2c04a64049199f69215fee4370 run #0: crashed: KASAN: use-after-free Read in ext4_ext_remove_space run #1: crashed: KASAN: use-after-free Write in ext4_ext_remove_space run #2: crashed: KASAN: use-after-free Read in ext4_ext_insert_extent run #3: crashed: KASAN: out-of-bounds Read in ext4_ext_remove_space run #4: crashed: KASAN: slab-out-of-bounds Read in ext4_ext_insert_extent run #5: crashed: KASAN: use-after-free Write in ext4_ext_remove_space run #6: crashed: KASAN: use-after-free Write in ext4_ext_remove_space run #7: crashed: KASAN: use-after-free Read in ext4_find_extent run #8: crashed: KASAN: use-after-free Read in ext4_find_extent run #9: crashed: KASAN: use-after-free Read in ext4_ext_insert_extent representative crash: KASAN: use-after-free Read in ext4_ext_remove_space, types: [KASAN-USE-AFTER-FREE-READ KASAN-USE-AFTER-FREE-WRITE] 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 fc9aa81462ee32fea3dd6d7c6d8d7dcdb69637df gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.44 failed building fc9aa81462ee32fea3dd6d7c6d8d7dcdb69637df: net/socket.c:1128:(.text+0x1307): undefined reference to `wext_handle_ioctl' net/socket.c:3397:(.text+0x17c7): undefined reference to `compat_wext_handle_ioctl' net/core/net-procfs.c:346:(.text+0x33b): undefined reference to `wext_proc_exit' net/core/net-procfs.c:330:(.text+0x4e2): undefined reference to `wext_proc_init' minimized to 46 configs; suspects: [HID_ZEROPLUS 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 [ubsan bug_or_warning locking atomic_sleep hang memleak], they are not needed testing current HEAD 447db0046f21df411c817f9f05b9f6210adb9d81 testing commit 447db0046f21df411c817f9f05b9f6210adb9d81 gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.44 kernel signature: 6eb8877cf93b89379c6d048b66232ca8826e55135af3be487ceb2ae3b048c5dd run #0: crashed: KASAN: use-after-free Read in ext4_ext_insert_extent run #1: crashed: KASAN: use-after-free Read in ext4_ext_remove_space run #2: crashed: KASAN: use-after-free Read in ext4_ext_remove_space run #3: crashed: KASAN: use-after-free Read in ext4_ext_insert_extent run #4: crashed: KASAN: use-after-free Read in ext4_ext_remove_space run #5: crashed: KASAN: use-after-free Read in ext4_ext_remove_space run #6: crashed: KASAN: use-after-free Write in ext4_ext_remove_space run #7: crashed: KASAN: use-after-free Read in ext4_ext_remove_space run #8: crashed: KASAN: use-after-free Write in ext4_ext_remove_space run #9: crashed: KASAN: use-after-free Read in ext4_ext_insert_extent representative crash: KASAN: use-after-free Read in ext4_ext_insert_extent, types: [KASAN-USE-AFTER-FREE-READ] crash still not fixed/happens on the oldest tested release revisions tested: 7, total time: 2h17m33.961229328s (build: 1h8m17.997086932s, test: 50m30.225809081s) crash still not fixed or there were kernel test errors commit msg: Merge 39ca700c8ac0 ("crypto: af_alg - Remove zero-copy support from skcipher and aead") into android13-5.10-lts crash: KASAN: use-after-free Read in ext4_ext_insert_extent ================================================================== BUG: KASAN: use-after-free in ext4_ext_insert_extent+0x349c/0x3e70 fs/ext4/extents.c:2087 Read of size 4 at addr ffff88812ad88848 by task syz.6.16/546 CPU: 1 PID: 546 Comm: syz.6.16 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026 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 __asan_report_load4_noabort+0x14/0x20 mm/kasan/report_generic.c:308 ext4_ext_insert_extent+0x349c/0x3e70 fs/ext4/extents.c:2087 ext4_ext_map_blocks+0xfd6/0x52d0 fs/ext4/extents.c:4387 ext4_map_blocks+0x58d/0x1430 fs/ext4/inode.c:676 _ext4_get_block+0x206/0x5b0 fs/ext4/inode.c:819 ext4_get_block+0x11/0x20 fs/ext4/inode.c:836 ext4_block_write_begin+0x3b9/0xdc0 fs/ext4/inode.c:1103 ext4_write_begin+0x484/0xf00 fs/ext4/inode.c:1245 ext4_da_write_begin+0x52b/0xc30 fs/ext4/inode.c:3035 generic_perform_write+0x202/0x4a0 mm/filemap.c:3509 ext4_buffered_write_iter+0x1e5/0x420 fs/ext4/file.c:271 ext4_file_write_iter+0x358/0x18e0 fs/ext4/file.c:685 call_write_iter include/linux/fs.h:2066 [inline] new_sync_write+0x358/0x6d0 fs/read_write.c:518 vfs_write+0x4e4/0x750 fs/read_write.c:605 ksys_write+0x111/0x210 fs/read_write.c:658 __do_sys_write fs/read_write.c:670 [inline] __se_sys_write fs/read_write.c:667 [inline] __x64_sys_write+0x6e/0xb0 fs/read_write.c:667 do_syscall_64+0x32/0x80 arch/x86/entry/common.c:46 entry_SYSCALL_64_after_hwframe+0x61/0xcb RIP: 0033:0x7f3ecda158f9 Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f3ecd45c028 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 00007f3ecdc44080 RCX: 00007f3ecda158f9 RDX: 00000000002a979d RSI: 0000400000000000 RDI: 0000000000000004 RBP: 00007f3ecdaa71bc R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007f3ecdc44080 R15: 00007ffc271d6c48 The buggy address belongs to the page: page:ffffea0004ab6200 refcount:1 mapcount:1 mapping:0000000000000000 index:0x400000216 pfn:0x12ad88 anon flags: 0x4000000000080014(uptodate|lru|swapbacked) raw: 4000000000080014 ffffea0004ab61c8 ffffea0004ab6248 ffff8881106f95c1 raw: 0000000400000216 0000000000000000 0000000100000000 ffff88811528e000 page dumped because: kasan: bad access detected page->mem_cgroup:ffff88811528e000 page_owner tracks the page as allocated page last allocated via order 0, migratetype Movable, gfp_mask 0x8100dca(GFP_HIGHUSER_MOVABLE|__GFP_ZERO|0x8000000), pid 535, ts 41313314444, free_ts 0 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/0x2540 mm/page_alloc.c:5384 __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+0x16f1/0x3230 mm/memory.c:4795 __handle_mm_fault+0xac7/0xfa0 mm/memory.c:4953 handle_mm_fault+0x1b8/0x6b0 mm/memory.c:5367 do_user_addr_fault+0x562/0xd70 arch/x86/mm/fault.c:1343 handle_page_fault arch/x86/mm/fault.c:1436 [inline] exc_page_fault+0x65/0xc0 arch/x86/mm/fault.c:1492 asm_exc_page_fault+0x1e/0x30 arch/x86/include/asm/idtentry.h:571 page_owner free stack trace missing Memory state around the buggy address: ffff88812ad88700: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff88812ad88780: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffff88812ad88800: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ^ ffff88812ad88880: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff88812ad88900: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ================================================================== EXT4-fs error (device loop6): ext4_ext_split:1142: inode #17: comm syz.6.16: eh_entries 41222 != eh_max 37016! EXT4-fs error (device loop6): ext4_free_blocks:5689: comm syz.6.16: Freeing blocks not in datazone - block = 78633974886736, count = 10298 EXT4-fs error (device loop6): ext4_free_blocks:5689: comm syz.6.16: Freeing blocks not in datazone - block = 51570670797377, count = 195 EXT4-fs error (device loop6): ext4_free_blocks:5689: comm syz.6.16: Freeing blocks not in datazone - block = 217489169814476, count = 26216 EXT4-fs error (device loop6): ext4_free_blocks:5689: comm syz.6.16: Freeing blocks not in datazone - block = 226604173524263, count = 12071 EXT4-fs error (device loop6): ext4_free_blocks:5689: comm syz.6.16: Freeing blocks not in datazone - block = 93049388264316, count = 30338 EXT4-fs error (device loop6): ext4_free_blocks:5689: comm syz.6.16: Freeing blocks not in datazone - block = 82673436927970, count = 7699 EXT4-fs error (device loop6): ext4_free_blocks:5689: comm syz.6.16: Freeing blocks not in datazone - block = 119206648149266, count = 29992 EXT4-fs error (device loop6): ext4_free_blocks:5689: comm syz.6.16: Freeing blocks not in datazone - block = 272701907145594, count = 7931 EXT4-fs error (device loop6): ext4_free_blocks:5689: comm syz.6.16: Freeing blocks not in datazone - block = 133631496427565, count = 20411