ci2 starts bisection 2026-01-02 22:18:22.749496138 +0000 UTC m=+3228514.926619225 bisecting fixing commit since d2bafcf224f3911b183113b2fcb536c9e90684a3 building syzkaller on d7d323527f8e6073ec1da024a08c26f50626254f ensuring issue is reproducible on original commit d2bafcf224f3911b183113b2fcb536c9e90684a3 testing commit d2bafcf224f3911b183113b2fcb536c9e90684a3 gcc compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 kernel signature: 2b4ca50eec4f4e099f135fb5ce92e4f536f483aa6b5b8230700949bce16a4d75 all runs: crashed: KASAN: use-after-free Read in ext4_inlinedir_to_tree representative crash: KASAN: use-after-free Read in ext4_inlinedir_to_tree, 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 d2bafcf224f3911b183113b2fcb536c9e90684a3 gcc compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 kernel signature: 6f4ac0359edb877c7f4188d68448dba9f974da851b488bd76328b44c3bfb6ac2 all runs: crashed: KASAN: use-after-free Read in ext4_inlinedir_to_tree representative crash: KASAN: use-after-free Read in ext4_inlinedir_to_tree, types: [KASAN-USE-AFTER-FREE-READ] 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=4109 full=8129 leaves diff=2157 split chunks (needed=false): <2157> split chunk #0 of len 2157 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 d2bafcf224f3911b183113b2fcb536c9e90684a3 gcc compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 kernel signature: d1657437a9f6d482b68108aa4e6b93298fdb45a299c9f5487870e9b087eabc61 all runs: crashed: KASAN: use-after-free Read in ext4_read_inline_data representative crash: KASAN: use-after-free Read in ext4_read_inline_data, 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 d2bafcf224f3911b183113b2fcb536c9e90684a3 gcc compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 kernel signature: f558d2823a76baa37d24aa0044c78f62656846ac8bedbd48d4a469cbb2ded5f0 all runs: crashed: KASAN: use-after-free Read in ext4_read_inline_data representative crash: KASAN: use-after-free Read in ext4_read_inline_data, types: [KASAN-USE-AFTER-FREE-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 d2bafcf224f3911b183113b2fcb536c9e90684a3 gcc compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 kernel signature: d7e349a803950b94458ab29d644667195733fb94297ca081fe01d5f3e120519f all runs: crashed: KASAN: use-after-free Read in ext4_read_inline_data representative crash: KASAN: use-after-free Read in ext4_read_inline_data, 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 d2bafcf224f3911b183113b2fcb536c9e90684a3 gcc compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 kernel signature: 00cb2d0f629531f8e99462b93d3a947418f61b85d49b4b3613b9afcedbf2d907 all runs: crashed: KASAN: use-after-free Read in ext4_read_inline_data representative crash: KASAN: use-after-free Read in ext4_read_inline_data, 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 d2bafcf224f3911b183113b2fcb536c9e90684a3 gcc compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 kernel signature: 054365e83c8e64a5ebfe68516b04b7e157d5c6d2f2c0ee36c67b4d0d04456643 all runs: crashed: KASAN: use-after-free Read in ext4_read_inline_data representative crash: KASAN: use-after-free Read in ext4_read_inline_data, types: [KASAN-USE-AFTER-FREE-READ] the chunk can be dropped disabling configs for [locking atomic_sleep hang memleak ubsan bug_or_warning], they are not needed testing current HEAD bbbc721033c076bad736c48a2b9f75bee4003607 testing commit bbbc721033c076bad736c48a2b9f75bee4003607 gcc compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 kernel signature: 877d278baf3dc8792f4bd8a27ce3c8541c5c3ded7d07c310b6cae5d0e59e8ed8 all runs: crashed: KASAN: use-after-free Read in ext4_read_inline_data representative crash: KASAN: use-after-free Read in ext4_read_inline_data, types: [KASAN-USE-AFTER-FREE-READ] crash still not fixed/happens on the oldest tested release revisions tested: 8, total time: 1h49m31.082230391s (build: 52m18.415633881s, test: 49m3.632379952s) crash still not fixed or there were kernel test errors commit msg: Merge tag 'pm-6.19-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm crash: KASAN: use-after-free Read in ext4_read_inline_data EXT4-fs error (device loop0): htree_dirblock_to_tree:1080: inode #2: block 21: comm syz-executor: bad entry in directory: directory entry overrun - offset=1004, inode=0, rec_len=1000, size=1024 fake=0 ================================================================== BUG: KASAN: use-after-free in ext4_read_inline_data+0x18f/0x280 fs/ext4/inline.c:214 Read of size 324 at addr ffff88812a21fc05 by task syz-executor/2384 CPU: 1 UID: 0 PID: 2384 Comm: syz-executor Not tainted syzkaller #0 PREEMPT(none) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025 Call Trace: dump_stack_lvl+0x52/0x80 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 check_region_inline mm/kasan/generic.c:-1 [inline] kasan_check_range+0x2b0/0x2c0 mm/kasan/generic.c:200 __asan_memcpy+0x29/0x70 mm/kasan/shadow.c:105 ext4_read_inline_data+0x18f/0x280 fs/ext4/inline.c:214 ext4_inlinedir_to_tree+0x2d8/0xae0 fs/ext4/inline.c:1286 ext4_htree_fill_tree+0x3d9/0xf70 fs/ext4/namei.c:1179 ext4_dx_readdir fs/ext4/dir.c:601 [inline] ext4_readdir+0x24e3/0x2fc0 fs/ext4/dir.c:146 iterate_dir+0x1aa/0x4c0 fs/readdir.c:108 __do_sys_getdents64 fs/readdir.c:410 [inline] __se_sys_getdents64+0xd3/0x1b0 fs/readdir.c:396 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x85/0x2e0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f64b8e9c013 Code: c1 66 0f 1f 44 00 00 48 83 c4 08 48 89 ef 5b 5d e9 52 43 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:00007ffc6a938cb8 EFLAGS: 00000293 ORIG_RAX: 00000000000000d9 RAX: ffffffffffffffda RBX: 000055558e5da520 RCX: 00007f64b8e9c013 RDX: 0000000000008000 RSI: 000055558e5da520 RDI: 0000000000000006 RBP: 000055558e5da4f4 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000001000 R11: 0000000000000293 R12: ffffffffffffffa8 R13: 0000000000000016 R14: 000055558e5da4f0 R15: 00007ffc6a93c050 The buggy address belongs to the physical page: page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x1d0 pfn:0x12a21f flags: 0x200000000000000(node=0|zone=2) raw: 0200000000000000 ffffea0004a88388 ffffea0004a88b48 0000000000000000 raw: 00000000000001d0 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 2086, tgid 2086 (modprobe), ts 69848981481, free_ts 69851719503 set_page_owner include/linux/page_owner.h:32 [inline] post_alloc_hook+0x15a/0x190 mm/page_alloc.c:1857 prep_new_page mm/page_alloc.c:1865 [inline] get_page_from_freelist+0x297f/0x2af0 mm/page_alloc.c:3915 __alloc_frozen_pages_noprof+0x26b/0x460 mm/page_alloc.c:5210 alloc_pages_mpol+0xcb/0x270 mm/mempolicy.c:2486 folio_alloc_mpol_noprof mm/mempolicy.c:2505 [inline] vma_alloc_folio_noprof+0x288/0x400 mm/mempolicy.c:2540 folio_prealloc+0x24/0xf0 mm/memory.c:-1 wp_page_copy mm/memory.c:3719 [inline] do_wp_page+0xc2d/0x2ef0 mm/memory.c:4180 handle_pte_fault mm/memory.c:6289 [inline] __handle_mm_fault mm/memory.c:6411 [inline] handle_mm_fault+0x872/0x2320 mm/memory.c:6580 do_user_addr_fault+0x31a/0xc30 arch/x86/mm/fault.c:1336 handle_page_fault arch/x86/mm/fault.c:1476 [inline] exc_page_fault+0x62/0xa0 arch/x86/mm/fault.c:1532 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:618 page last free pid 2086 tgid 2086 stack trace: reset_page_owner include/linux/page_owner.h:25 [inline] free_pages_prepare mm/page_alloc.c:1406 [inline] free_unref_folios+0xcdd/0x12d0 mm/page_alloc.c:3000 folios_put_refs+0x319/0x400 mm/swap.c:1002 free_pages_and_swap_cache+0x20d/0x3c0 mm/swap_state.c:355 __tlb_batch_free_encoded_pages mm/mmu_gather.c:136 [inline] tlb_batch_pages_flush mm/mmu_gather.c:149 [inline] tlb_flush_mmu_free mm/mmu_gather.c:397 [inline] tlb_flush_mmu+0x2ba/0x500 mm/mmu_gather.c:404 tlb_finish_mmu+0xaa/0x190 mm/mmu_gather.c:497 exit_mmap+0x374/0x830 mm/mmap.c:1290 __mmput+0x62/0x290 kernel/fork.c:1173 exit_mm+0x11b/0x1b0 kernel/exit.c:581 do_exit+0x4f6/0x1d40 kernel/exit.c:959 do_group_exit+0x1b1/0x280 kernel/exit.c:1112 __do_sys_exit_group kernel/exit.c:1123 [inline] __se_sys_exit_group kernel/exit.c:1121 [inline] __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1121 __pfx_local_irq_disable_exit_to_user+0x0/0x10 arch/x86/include/generated/asm/syscalls_64.h:232 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x85/0x2e0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f Memory state around the buggy address: ffff88812a21fb00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff88812a21fb80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >ffff88812a21fc00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ^ ffff88812a21fc80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff88812a21fd00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ==================================================================