ci2 starts bisection 2025-04-11 21:24:07.979540663 +0000 UTC m=+4814.403026151 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 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: f97c66f7523640b0c4ea44cd107bad24ac92119b8b36781dd5999b34fdd36f23 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] check whether we can drop unnecessary instrumentation disabling configs for [HANG LEAK UBSAN BUG LOCKDEP ATOMIC_SLEEP], they are not needed testing commit d2bafcf224f3911b183113b2fcb536c9e90684a3 gcc compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: 674a82a19eaa73ac7ab28ae2728e126b77b42da7bf01e9ac8a0cd7cc7271e2fd 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] the bug reproduces without the instrumentation disabling configs for [UBSAN BUG LOCKDEP ATOMIC_SLEEP HANG LEAK], they are not needed kconfig minimization: base=4071 full=8129 leaves diff=2129 split chunks (needed=false): <2129> split chunk #0 of len 2129 into 5 parts testing without sub-chunk 1/5 disabling configs for [LOCKDEP ATOMIC_SLEEP HANG LEAK UBSAN BUG], they are not needed testing commit d2bafcf224f3911b183113b2fcb536c9e90684a3 gcc compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: 8633ef423f50c1082281557cda0bd39ace8ae9e9310d90c85a878a7618a40c12 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] the chunk can be dropped testing without sub-chunk 2/5 disabling configs for [ATOMIC_SLEEP HANG LEAK UBSAN BUG LOCKDEP], they are not needed testing commit d2bafcf224f3911b183113b2fcb536c9e90684a3 gcc compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: aad17b8cd2da868f5eff4aba13cf79ebb9b857e7fb2dc9c4deea6ef94ac6c16d run #0: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #1: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #2: crashed: BUG: unable to handle kernel paging request in ext4_read_inline_data run #3: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #4: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #5: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #6: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #7: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #8: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #9: 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] the chunk can be dropped testing without sub-chunk 3/5 disabling configs for [BUG LOCKDEP ATOMIC_SLEEP HANG LEAK UBSAN], they are not needed testing commit d2bafcf224f3911b183113b2fcb536c9e90684a3 gcc compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: 4c1c51b3e3ca9436d506ce1f0d6a9ac090a7c3747a4e5869371e69cfca01d1a0 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] the chunk can be dropped testing without sub-chunk 4/5 disabling configs for [UBSAN BUG LOCKDEP ATOMIC_SLEEP HANG LEAK], they are not needed testing commit d2bafcf224f3911b183113b2fcb536c9e90684a3 gcc compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: 393375f1f7a41645b6a4fbdb3485ec5b901de2e0576ae2a75f1a1f2e61e089ac 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] the chunk can be dropped testing without sub-chunk 5/5 disabling configs for [BUG LOCKDEP ATOMIC_SLEEP HANG LEAK UBSAN], they are not needed testing commit d2bafcf224f3911b183113b2fcb536c9e90684a3 gcc compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: 124101ae2e6aa8342e05195516b7f473d0267d5e93a6fc7885caa92f715eea05 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] the chunk can be dropped disabling configs for [ATOMIC_SLEEP HANG LEAK UBSAN BUG LOCKDEP], they are not needed testing current HEAD e618ee89561b6b0fdc69f79e6fd0c33375d3e6b4 testing commit e618ee89561b6b0fdc69f79e6fd0c33375d3e6b4 gcc compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: 05c3999e9c1d2720e94ae1245176f7bf18b34fd19c026f7a90cc097b17378e86 run #0: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #1: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #2: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #3: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #4: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #5: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #6: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #7: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #8: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #9: 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] crash still not fixed/happens on the oldest tested release revisions tested: 8, total time: 2h39m3.496235637s (build: 1h56m30.688613605s, test: 36m0.164647815s) crash still not fixed or there were kernel test errors commit msg: Merge tag 'spi-fix-v6.15-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi crash: KASAN: use-after-free Read in ext4_read_inline_data EXT4-fs error (device loop0): htree_dirblock_to_tree:1082: 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+0x1ab/0x280 fs/ext4/inline.c:214 Read of size 324 at addr ffff888128acec05 by task syz-executor/1953 CPU: 0 UID: 0 PID: 1953 Comm: syz-executor Not tainted 6.15.0-rc1-syzkaller #0 PREEMPT(undef) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x10a/0x280 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:408 [inline] print_report+0x16e/0x5b0 mm/kasan/report.c:521 kasan_report+0x143/0x180 mm/kasan/report.c:634 check_region_inline mm/kasan/generic.c:-1 [inline] kasan_check_range+0x28f/0x2a0 mm/kasan/generic.c:189 __asan_memcpy+0x29/0x70 mm/kasan/shadow.c:105 ext4_read_inline_data+0x1ab/0x280 fs/ext4/inline.c:214 ext4_inlinedir_to_tree+0x2fa/0xe30 fs/ext4/inline.c:1301 ext4_htree_fill_tree+0x4dd/0x1240 fs/ext4/namei.c:1181 ext4_dx_readdir fs/ext4/dir.c:601 [inline] ext4_readdir+0x2545/0x2fc0 fs/ext4/dir.c:146 iterate_dir+0x18e/0x490 fs/readdir.c:108 __do_sys_getdents64 fs/readdir.c:403 [inline] __se_sys_getdents64+0x1d9/0x430 fs/readdir.c:389 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x8d/0x170 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f914517c013 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:00007ffd5834f3d8 EFLAGS: 00000293 ORIG_RAX: 00000000000000d9 RAX: ffffffffffffffda RBX: 0000555594f66520 RCX: 00007f914517c013 RDX: 0000000000008000 RSI: 0000555594f66520 RDI: 0000000000000006 RBP: 0000555594f664f4 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000001000 R11: 0000000000000293 R12: ffffffffffffffa8 R13: 0000000000000016 R14: 0000555594f664f0 R15: 00007ffd58352770 The buggy address belongs to the physical page: page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x55f71b48f pfn:0x128ace flags: 0x200000000000000(node=0|zone=2) raw: 0200000000000000 ffffea0004a2b3c8 ffffea0004994448 0000000000000000 raw: 000000055f71b48f 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 1906, tgid 1906 (udevd), ts 64058792529, free_ts 67769773608 set_page_owner include/linux/page_owner.h:32 [inline] post_alloc_hook+0x108/0x120 mm/page_alloc.c:1717 prep_new_page mm/page_alloc.c:1725 [inline] get_page_from_freelist+0x3e26/0x40c0 mm/page_alloc.c:3652 __alloc_frozen_pages_noprof+0x252/0x700 mm/page_alloc.c:4934 alloc_pages_mpol+0x14f/0x3c0 mm/mempolicy.c:2301 folio_alloc_mpol_noprof mm/mempolicy.c:2320 [inline] vma_alloc_folio_noprof+0x2b8/0x430 mm/mempolicy.c:2355 folio_prealloc+0x23/0xf0 mm/memory.c:-1 wp_page_copy mm/memory.c:3478 [inline] do_wp_page+0xb6c/0x3080 mm/memory.c:3939 handle_pte_fault mm/memory.c:6013 [inline] __handle_mm_fault mm/memory.c:6140 [inline] handle_mm_fault+0x1823/0x34e0 mm/memory.c:6309 do_user_addr_fault arch/x86/mm/fault.c:1337 [inline] handle_page_fault arch/x86/mm/fault.c:1480 [inline] exc_page_fault+0x3fa/0x7b0 arch/x86/mm/fault.c:1538 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623 page last free pid 1906 tgid 1906 stack trace: reset_page_owner include/linux/page_owner.h:25 [inline] free_pages_prepare mm/page_alloc.c:1262 [inline] free_unref_folios+0xbfb/0x1450 mm/page_alloc.c:2737 folios_put_refs+0x429/0x530 mm/swap.c:992 free_pages_and_swap_cache+0x27a/0x4e0 mm/swap_state.c:267 __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+0x2b3/0x500 mm/mmu_gather.c:404 tlb_finish_mmu+0xb6/0x1c0 mm/mmu_gather.c:496 exit_mmap+0x48b/0xa50 mm/mmap.c:1297 __mmput+0x61/0x290 kernel/fork.c:1379 exit_mm+0x114/0x1b0 kernel/exit.c:589 do_exit+0x7bb/0x24f0 kernel/exit.c:940 do_group_exit+0x1ba/0x280 kernel/exit.c:1102 __do_sys_exit_group kernel/exit.c:1113 [inline] __se_sys_exit_group kernel/exit.c:1111 [inline] __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1111 x64_sys_call+0x26c3/0x26d0 arch/x86/include/generated/asm/syscalls_64.h:232 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x8d/0x170 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f Memory state around the buggy address: ffff888128aceb00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff888128aceb80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >ffff888128acec00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ^ ffff888128acec80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff888128aced00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ==================================================================