ci2 starts bisection 2025-03-07 06:21:50.196272082 +0000 UTC m=+116587.285437753 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: c274d66b7910be5219eb65cc6938111f36474903a3f286971c8ae3a01962aaba run #0: crashed: WARNING in call_timer_fn run #1: crashed: KASAN: use-after-free Read in ext4_inlinedir_to_tree run #2: crashed: KASAN: use-after-free Read in ext4_inlinedir_to_tree run #3: crashed: KASAN: use-after-free Read in ext4_inlinedir_to_tree run #4: crashed: KASAN: use-after-free Read in ext4_inlinedir_to_tree run #5: crashed: KASAN: use-after-free Read in ext4_inlinedir_to_tree run #6: crashed: KASAN: use-after-free Read in ext4_inlinedir_to_tree run #7: crashed: KASAN: use-after-free Read in ext4_inlinedir_to_tree run #8: crashed: KASAN: use-after-free Read in ext4_inlinedir_to_tree run #9: crashed: KASAN: use-after-free Read in ext4_inlinedir_to_tree run #10: crashed: KASAN: use-after-free Read in ext4_inlinedir_to_tree run #11: crashed: KASAN: use-after-free Read in ext4_inlinedir_to_tree run #12: crashed: KASAN: use-after-free Read in ext4_inlinedir_to_tree run #13: crashed: KASAN: use-after-free Read in ext4_inlinedir_to_tree run #14: crashed: KASAN: use-after-free Read in ext4_inlinedir_to_tree run #15: crashed: KASAN: use-after-free Read in ext4_inlinedir_to_tree run #16: crashed: KASAN: use-after-free Read in ext4_inlinedir_to_tree run #17: crashed: KASAN: use-after-free Read in ext4_inlinedir_to_tree run #18: crashed: KASAN: use-after-free Read in ext4_inlinedir_to_tree run #19: 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 [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: 2cdc97b581ced09a8aee494a0580dc50b5bc7460c91872f05325b4344ef6e50b 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 [BUG LOCKDEP ATOMIC_SLEEP HANG LEAK UBSAN], they are not needed kconfig minimization: base=4054 full=8129 leaves diff=2118 split chunks (needed=false): <2118> split chunk #0 of len 2118 into 5 parts testing without sub-chunk 1/5 disabling configs for [LEAK UBSAN BUG LOCKDEP ATOMIC_SLEEP HANG], 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: ff0fc6fb98e63c7cb8e90f706190c17d4a039c45cc157e74d36ea33a8fe178e2 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: 8e162253d73e3969d9721f30c21e111c0092c6b95acee2990923bd4bdc196acd 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 3/5 disabling configs for [LEAK UBSAN BUG LOCKDEP ATOMIC_SLEEP HANG], 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: 616001d38e694e1c19ef0aebd4f5fbf2e0a41ae923d3799c25bcd0d7f2933ea8 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: aff541569f939b3481c299cd392e32b12c97fc7d09480aa52b1247a75a41f78c 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 [LEAK UBSAN BUG LOCKDEP ATOMIC_SLEEP HANG], 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: 223e8bcbf2961c164de1619f8740f235640ec3847fa754b77912786a20d219f6 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 [BUG LOCKDEP ATOMIC_SLEEP HANG LEAK UBSAN], they are not needed testing current HEAD 00a7d39898c8010bfd5ff62af31ca5db34421b38 testing commit 00a7d39898c8010bfd5ff62af31ca5db34421b38 gcc compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: 23b309a7e6f1d8e964ad5ba6fb66db5f544d73c33912460ca16d591d514c0342 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] crash still not fixed/happens on the oldest tested release revisions tested: 8, total time: 1h33m53.794849768s (build: 52m11.942806559s, test: 36m41.716778257s) crash still not fixed or there were kernel test errors commit msg: fs/pipe: add simpler helpers for common cases crash: KASAN: use-after-free Read in ext4_read_inline_data EXT4-fs error (device loop0): htree_dirblock_to_tree:1112: 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+0x1a5/0x280 fs/ext4/inline.c:209 Read of size 324 at addr ffff88812617bc05 by task syz-executor/2409 CPU: 1 UID: 0 PID: 2409 Comm: syz-executor Not tainted 6.14.0-rc5-syzkaller #0 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+0x108/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 kasan_check_range+0x282/0x290 mm/kasan/generic.c:189 __asan_memcpy+0x29/0x70 mm/kasan/shadow.c:105 ext4_read_inline_data+0x1a5/0x280 fs/ext4/inline.c:209 ext4_inlinedir_to_tree+0x2f6/0xe10 fs/ext4/inline.c:1366 ext4_htree_fill_tree+0x4db/0x1240 fs/ext4/namei.c:1211 ext4_dx_readdir fs/ext4/dir.c:598 [inline] ext4_readdir+0x253c/0x2fb0 fs/ext4/dir.c:143 iterate_dir+0x18e/0x490 fs/readdir.c:108 __do_sys_getdents64 fs/readdir.c:403 [inline] __se_sys_getdents64+0x1b3/0x400 fs/readdir.c:389 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x8d/0x170 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f7e76c8c013 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:00007ffef2d8e748 EFLAGS: 00000293 ORIG_RAX: 00000000000000d9 RAX: ffffffffffffffda RBX: 0000555569fc0520 RCX: 00007f7e76c8c013 RDX: 0000000000008000 RSI: 0000555569fc0520 RDI: 0000000000000006 RBP: 0000555569fc04f4 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000001000 R11: 0000000000000293 R12: ffffffffffffffa8 R13: 0000000000000016 R14: 0000555569fc04f0 R15: 00007ffef2d91ae0 The buggy address belongs to the physical page: page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x55d001d5e pfn:0x12617b flags: 0x200000000000000(node=0|zone=2) raw: 0200000000000000 ffffea0004981688 ffffea0004985e88 0000000000000000 raw: 000000055d001d5e 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 2374, tgid 2374 (udevd), ts 62384448453, free_ts 65806595404 set_page_owner include/linux/page_owner.h:32 [inline] post_alloc_hook+0x108/0x120 mm/page_alloc.c:1551 prep_new_page mm/page_alloc.c:1559 [inline] get_page_from_freelist+0x3b4a/0x3d80 mm/page_alloc.c:3477 __alloc_frozen_pages_noprof+0x256/0x650 mm/page_alloc.c:4739 alloc_pages_mpol+0x14d/0x3b0 mm/mempolicy.c:2270 folio_alloc_mpol_noprof mm/mempolicy.c:2289 [inline] vma_alloc_folio_noprof+0x2b9/0x430 mm/mempolicy.c:2324 folio_prealloc+0x23/0xf0 wp_page_copy mm/memory.c:3446 [inline] do_wp_page+0xb6d/0x2f40 mm/memory.c:3838 handle_pte_fault mm/memory.c:5916 [inline] __handle_mm_fault mm/memory.c:6043 [inline] handle_mm_fault+0x1645/0x3230 mm/memory.c:6212 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/0x780 arch/x86/mm/fault.c:1538 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623 page last free pid 2374 tgid 2374 stack trace: reset_page_owner include/linux/page_owner.h:25 [inline] free_pages_prepare mm/page_alloc.c:1127 [inline] free_unref_folios+0xb24/0x1340 mm/page_alloc.c:2707 folios_put_refs+0x409/0x510 mm/swap.c:994 free_pages_and_swap_cache+0x275/0x4d0 mm/swap_state.c:331 __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:389 [inline] tlb_flush_mmu+0x2ad/0x4e0 mm/mmu_gather.c:396 tlb_finish_mmu+0xb6/0x1c0 mm/mmu_gather.c:488 exit_mmap+0x48e/0xa40 mm/mmap.c:1297 __mmput+0x61/0x290 kernel/fork.c:1356 exit_mm+0x114/0x1b0 kernel/exit.c:570 do_exit+0x7d8/0x2550 kernel/exit.c:925 do_group_exit+0x1ba/0x280 kernel/exit.c:1087 __do_sys_exit_group kernel/exit.c:1098 [inline] __se_sys_exit_group kernel/exit.c:1096 [inline] __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1096 x64_sys_call+0x26a8/0x26b0 arch/x86/include/generated/asm/syscalls_64.h:232 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x8d/0x170 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Memory state around the buggy address: ffff88812617bb00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff88812617bb80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >ffff88812617bc00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ^ ffff88812617bc80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff88812617bd00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ==================================================================