ci2 starts bisection 2025-09-18 02:39:31.488992905 +0000 UTC m=+545083.363808032 bisecting fixing commit since d0c22de9995b624f563bc5004d44ac2655712a56 building syzkaller on ed351ea732d889c7798e7f0226bcaec65a8a6b52 ensuring issue is reproducible on original commit d0c22de9995b624f563bc5004d44ac2655712a56 testing commit d0c22de9995b624f563bc5004d44ac2655712a56 gcc compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 kernel signature: 38529d3ed36a0a28ea0815c32979cb1662ab715898b215cb3ddf923494771413 run #0: crashed: KASAN: slab-out-of-bounds Read in ext4_find_extent run #1: crashed: KASAN: use-after-free Read in ext4_find_extent run #2: crashed: KASAN: slab-out-of-bounds Read in ext4_ext_insert_extent run #3: crashed: KASAN: slab-use-after-free Read in ext4_find_extent run #4: crashed: KASAN: slab-use-after-free Read in ext4_ext_insert_extent run #5: crashed: KASAN: slab-out-of-bounds Read in ext4_find_extent run #6: crashed: KASAN: slab-use-after-free Read in ext4_find_extent run #7: crashed: KASAN: slab-use-after-free Read in ext4_find_extent run #8: crashed: KASAN: slab-use-after-free Read in ext4_find_extent run #9: crashed: KASAN: slab-out-of-bounds Read in ext4_find_extent run #10: crashed: KASAN: slab-out-of-bounds Read in ext4_find_extent run #11: crashed: KASAN: use-after-free Read in ext4_find_extent run #12: crashed: KASAN: slab-use-after-free Read in ext4_find_extent run #13: crashed: KASAN: slab-use-after-free Read in ext4_find_extent run #14: crashed: KASAN: use-after-free Read in ext4_find_extent run #15: crashed: KASAN: slab-out-of-bounds Read in ext4_find_extent run #16: crashed: KASAN: slab-use-after-free Read in ext4_find_extent run #17: crashed: KASAN: slab-use-after-free Read in ext4_find_extent run #18: crashed: KASAN: slab-use-after-free Read in ext4_ext_insert_extent run #19: crashed: KASAN: use-after-free Read in ext4_find_extent representative crash: KASAN: use-after-free Read in ext4_find_extent, 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 d0c22de9995b624f563bc5004d44ac2655712a56 gcc compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 kernel signature: 487f43181eb19420e2c80cec9bdf2eec9448050936660d4e488089728dc230d0 run #0: crashed: KASAN: slab-out-of-bounds Read in ext4_find_extent run #1: crashed: KASAN: use-after-free Read in ext4_find_extent run #2: crashed: KASAN: slab-out-of-bounds Read in ext4_ext_insert_extent run #3: crashed: KASAN: slab-use-after-free Read in ext4_find_extent run #4: crashed: KASAN: slab-use-after-free Read in ext4_find_extent run #5: crashed: KASAN: slab-use-after-free Read in ext4_ext_insert_extent run #6: crashed: KASAN: use-after-free Read in ext4_ext_insert_extent run #7: crashed: KASAN: slab-out-of-bounds Read in ext4_find_extent run #8: crashed: KASAN: slab-out-of-bounds Read in ext4_find_extent run #9: crashed: KASAN: slab-out-of-bounds Read in ext4_find_extent representative crash: KASAN: slab-out-of-bounds Read in ext4_find_extent, types: [KASAN-READ KASAN-USE-AFTER-FREE-READ] the bug reproduces without the instrumentation disabling configs for [ubsan bug_or_warning locking atomic_sleep hang memleak], they are not needed kconfig minimization: base=4092 full=8326 leaves diff=2136 split chunks (needed=false): <2136> split chunk #0 of len 2136 into 5 parts testing without sub-chunk 1/5 disabling configs for [bug_or_warning locking atomic_sleep hang memleak ubsan], they are not needed testing commit d0c22de9995b624f563bc5004d44ac2655712a56 gcc compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 kernel signature: 51324e4c43d7e04b6b29971b9b4dd62c04b06ea36b6bc9ba55301454e7a142c0 run #0: crashed: KASAN: slab-use-after-free Read in ext4_ext_insert_extent run #1: crashed: KASAN: use-after-free Read in ext4_find_extent run #2: crashed: KASAN: use-after-free Read in ext4_find_extent run #3: crashed: KASAN: slab-out-of-bounds Read in ext4_find_extent run #4: crashed: KASAN: use-after-free Read in ext4_find_extent run #5: crashed: KASAN: use-after-free Read in ext4_find_extent run #6: crashed: KASAN: use-after-free Read in ext4_find_extent 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: slab-use-after-free Read in ext4_find_extent representative crash: KASAN: slab-use-after-free Read in ext4_ext_insert_extent, types: [KASAN-USE-AFTER-FREE-READ] the chunk can be dropped testing without sub-chunk 2/5 disabling configs for [hang memleak ubsan bug_or_warning locking atomic_sleep], they are not needed testing commit d0c22de9995b624f563bc5004d44ac2655712a56 gcc compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 kernel signature: 37a88b79fdd75c5774901182acb276c3cbc8fc286b7ef5994cbb2b9c1de39dd9 run #0: crashed: KASAN: slab-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: slab-out-of-bounds Read in ext4_find_extent run #3: crashed: KASAN: use-after-free Read in ext4_find_extent run #4: crashed: KASAN: slab-use-after-free Read in ext4_find_extent run #5: crashed: KASAN: slab-use-after-free Read in ext4_find_extent run #6: crashed: KASAN: slab-out-of-bounds Read in ext4_find_extent run #7: crashed: KASAN: slab-out-of-bounds Read in ext4_find_extent run #8: crashed: KASAN: use-after-free Read in ext4_ext_correct_indexes run #9: crashed: KASAN: slab-use-after-free Read in ext4_find_extent representative crash: KASAN: slab-use-after-free Read in ext4_ext_insert_extent, types: [KASAN-USE-AFTER-FREE-READ KASAN-READ] the chunk can be dropped testing without sub-chunk 3/5 disabling configs for [locking atomic_sleep hang memleak ubsan bug_or_warning], they are not needed testing commit d0c22de9995b624f563bc5004d44ac2655712a56 gcc compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 kernel signature: 28b9caa8a0ba581ed56789e48636ef48ac6173179d0163e0a6fae2af71b5ccbf run #0: crashed: KASAN: slab-use-after-free Read in ext4_find_extent run #1: crashed: KASAN: use-after-free Read in ext4_find_extent run #2: crashed: KASAN: slab-out-of-bounds Read in ext4_find_extent run #3: crashed: KASAN: slab-out-of-bounds Read in ext4_find_extent run #4: crashed: KASAN: slab-out-of-bounds Read in ext4_ext_insert_extent run #5: crashed: KASAN: slab-use-after-free Read in ext4_find_extent run #6: crashed: KASAN: slab-out-of-bounds Read in ext4_find_extent run #7: crashed: KASAN: slab-out-of-bounds Read in ext4_find_extent run #8: crashed: KASAN: slab-use-after-free Read in ext4_ext_insert_extent run #9: crashed: KASAN: slab-use-after-free Read in ext4_find_extent representative crash: KASAN: slab-use-after-free Read in ext4_find_extent, types: [KASAN-USE-AFTER-FREE-READ KASAN-READ] the chunk can be dropped testing without sub-chunk 4/5 disabling configs for [hang memleak ubsan bug_or_warning locking atomic_sleep], they are not needed testing commit d0c22de9995b624f563bc5004d44ac2655712a56 gcc compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 kernel signature: 2cf7aa7d1d954ae4537641eaebcba40e4811a3928f7f848aedb69ef0e6df6177 run #0: crashed: KASAN: slab-use-after-free Read in ext4_ext_insert_extent run #1: crashed: KASAN: slab-use-after-free Read in ext4_ext_insert_extent run #2: crashed: KASAN: slab-out-of-bounds Read in ext4_ext_insert_extent run #3: crashed: KASAN: slab-out-of-bounds Read in ext4_ext_correct_indexes run #4: crashed: KASAN: slab-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: slab-out-of-bounds Read in ext4_find_extent run #7: crashed: KASAN: slab-out-of-bounds Read in ext4_ext_insert_extent run #8: crashed: KASAN: slab-use-after-free Read in ext4_find_extent run #9: crashed: KASAN: slab-use-after-free Read in ext4_ext_insert_extent representative crash: KASAN: slab-use-after-free Read in ext4_ext_insert_extent, types: [KASAN-USE-AFTER-FREE-READ KASAN-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 d0c22de9995b624f563bc5004d44ac2655712a56 gcc compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 kernel signature: bda11b72a86fd17750b8a1d9d62753f632364dfc33802f471b23bed167d85b21 run #0: crashed: KASAN: slab-use-after-free Read in ext4_ext_insert_extent run #1: crashed: KASAN: slab-use-after-free Read in ext4_find_extent run #2: crashed: KASAN: slab-use-after-free Read in ext4_ext_insert_extent run #3: crashed: KASAN: slab-out-of-bounds Read in ext4_ext_insert_extent run #4: crashed: KASAN: slab-use-after-free Read in ext4_ext_insert_extent run #5: crashed: KASAN: slab-use-after-free Read in ext4_ext_insert_extent run #6: crashed: KASAN: use-after-free Read in ext4_find_extent run #7: crashed: KASAN: slab-use-after-free Read in ext4_ext_correct_indexes run #8: crashed: KASAN: slab-out-of-bounds Read in ext4_ext_insert_extent run #9: crashed: KASAN: slab-out-of-bounds Read in ext4_find_extent representative crash: KASAN: slab-use-after-free Read in ext4_ext_insert_extent, types: [KASAN-USE-AFTER-FREE-READ KASAN-READ] the chunk can be dropped disabling configs for [bug_or_warning locking atomic_sleep hang memleak ubsan], they are not needed testing current HEAD 992d4e481e958c6898fe750afd429d1b585fff93 testing commit 992d4e481e958c6898fe750afd429d1b585fff93 gcc compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 kernel signature: 01e0fa06c168d53fd9a17408952c6bf80b7cd926d274ea350899a5a1b5680f17 run #0: crashed: KASAN: use-after-free Read in ext4_ext_insert_extent run #1: crashed: KASAN: slab-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: slab-out-of-bounds Read in ext4_ext_insert_extent run #4: crashed: KASAN: slab-out-of-bounds Read in ext4_find_extent run #5: crashed: KASAN: slab-use-after-free Read in ext4_find_extent run #6: crashed: KASAN: use-after-free Read in ext4_find_extent run #7: crashed: KASAN: use-after-free Read in ext4_ext_correct_indexes run #8: crashed: KASAN: slab-out-of-bounds Read in ext4_find_extent run #9: crashed: KASAN: slab-use-after-free Read in ext4_find_extent representative crash: KASAN: use-after-free Read in ext4_ext_insert_extent, types: [KASAN-USE-AFTER-FREE-READ KASAN-READ] crash still not fixed/happens on the oldest tested release revisions tested: 8, total time: 1h58m34.000398717s (build: 53m33.987773004s, test: 55m20.108856027s) crash still not fixed or there were kernel test errors commit msg: Merge tag 'probes-fixes-v6.17-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace crash: KASAN: use-after-free Read in ext4_ext_insert_extent EXT4-fs: Ignoring removed orlov option EXT4-fs (loop2): stripe (1570) is not aligned with cluster size (16), stripe is disabled EXT4-fs (loop2): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: writeback. ================================================================== BUG: KASAN: use-after-free in ext4_ext_insert_extent+0x3c34/0x4b70 fs/ext4/extents.c:2086 Read of size 4 at addr ffff88812f15dc18 by task syz.2.48/3339 CPU: 0 UID: 0 PID: 3339 Comm: syz.2.48 Not tainted syzkaller #0 PREEMPT(none) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025 Call Trace: dump_stack_lvl+0xf4/0x170 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xca/0x240 mm/kasan/report.c:482 kasan_report+0x118/0x150 mm/kasan/report.c:595 ext4_ext_insert_extent+0x3c34/0x4b70 fs/ext4/extents.c:2086 ext4_ext_map_blocks+0x1afd/0x5810 fs/ext4/extents.c:4404 ext4_map_create_blocks fs/ext4/inode.c:609 [inline] ext4_map_blocks+0x5cb/0x12d0 fs/ext4/inode.c:811 _ext4_get_block+0x19f/0x3d0 fs/ext4/inode.c:910 ext4_get_block_unwritten+0x17/0xa0 fs/ext4/inode.c:943 ext4_block_write_begin+0x754/0xcc0 fs/ext4/inode.c:1198 ext4_write_begin+0x8f7/0x13f0 fs/ext4/inode.c:-1 ext4_da_write_begin+0x2d7/0xa00 fs/ext4/inode.c:3129 generic_perform_write+0x26f/0x630 mm/filemap.c:4175 ext4_buffered_write_iter+0x2c3/0x510 fs/ext4/file.c:299 ext4_file_write_iter+0x201/0x1220 fs/ext4/file.c:-1 new_sync_write fs/read_write.c:593 [inline] vfs_write+0x56b/0xc70 fs/read_write.c:686 ksys_pwrite64 fs/read_write.c:793 [inline] __do_sys_pwrite64 fs/read_write.c:801 [inline] __se_sys_pwrite64 fs/read_write.c:798 [inline] __x64_sys_pwrite64+0x139/0x1c0 fs/read_write.c:798 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x8f/0x250 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f6fa703e969 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:00007f6fa6aaf038 EFLAGS: 00000246 ORIG_RAX: 0000000000000012 RAX: ffffffffffffffda RBX: 00007f6fa7265fa0 RCX: 00007f6fa703e969 RDX: 000000000000fdef RSI: 0000200000000140 RDI: 0000000000000004 RBP: 00007f6fa70c0ab1 R08: 0000000000000000 R09: 0000000000000000 R10: 000000000000fecc R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007f6fa7265fa0 R15: 00007ffc8316c018 The buggy address belongs to the physical page: page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x12f15d flags: 0x200000000000000(node=0|zone=2) raw: 0200000000000000 dead000000000100 dead000000000122 0000000000000000 raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000 page dumped because: kasan: bad access detected page_owner info is not present (never set?) Memory state around the buggy address: ffff88812f15db00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff88812f15db80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >ffff88812f15dc00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ^ ffff88812f15dc80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff88812f15dd00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ==================================================================