ci2 starts bisection 2025-07-18 01:58:23.909003644 +0000 UTC m=+126.610588328 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.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7 kernel signature: 84db1827f19d407009efefac336a743acf7dcf0e0f5490e96a9daa4b501c4946 run #0: crashed: KASAN: use-after-free Read in ext4_inlinedir_to_tree 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: out-of-bounds 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-USE-AFTER-FREE-READ] check whether we can drop unnecessary instrumentation disabling configs for [atomic_sleep hang memleak ubsan bug_or_warning locking], they are not needed testing commit d2bafcf224f3911b183113b2fcb536c9e90684a3 gcc compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7 kernel signature: 368e8595a06b00eb6504166967f9833cdcceb210a01ce14b5aac2b5a5dddf463 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 [locking atomic_sleep hang memleak ubsan bug_or_warning], they are not needed kconfig minimization: base=4088 full=8129 leaves diff=2143 split chunks (needed=false): <2143> split chunk #0 of len 2143 into 5 parts testing without sub-chunk 1/5 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.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7 kernel signature: a6b8ae44c634f3103d8651cc43c0c923ebae2dd17f38cbfe0dfb4ad1308ace3b 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.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7 kernel signature: 9464506a2e82c92a6cd0540fa0b16609ac7d8b6c1af313d5fc1955daec09b3e1 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.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7 kernel signature: 8b4851fa8b7d36af3a182d57e5d9e608d89f7c4b9a5ceda339a7212d94668a82 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 [memleak ubsan bug_or_warning locking atomic_sleep hang], they are not needed testing commit d2bafcf224f3911b183113b2fcb536c9e90684a3 gcc compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7 kernel signature: a19d2436bff4d8fdd208c65851e933a66a9107110db37730aae9742b17d1b994 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: 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: slab-out-of-bounds 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 [ubsan bug_or_warning locking atomic_sleep hang memleak], they are not needed testing commit d2bafcf224f3911b183113b2fcb536c9e90684a3 gcc compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7 kernel signature: b31cb64d5295c8fbef9ca950f09162f8b698ef886af10cd535cd598cf7344b59 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 [memleak ubsan bug_or_warning locking atomic_sleep hang], they are not needed testing current HEAD 6832a9317eee280117cd695fa885b2b7a7a38daf testing commit 6832a9317eee280117cd695fa885b2b7a7a38daf gcc compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7 kernel signature: 11d276823b1b5edf7552095def2e428c35a51758c7986d7aa6619dc3eb36ae25 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: 3h46m38.282928968s (build: 54m9.554841301s, test: 47m54.733645827s) crash still not fixed or there were kernel test errors commit msg: Merge tag 'net-6.16-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net 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 ffff88812c174c05 by task syz-executor/1980 CPU: 0 UID: 0 PID: 1980 Comm: syz-executor Not tainted 6.16.0-rc6-syzkaller #0 PREEMPT(none) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/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/0x230 mm/kasan/report.c:480 kasan_report+0x118/0x150 mm/kasan/report.c:593 check_region_inline mm/kasan/generic.c:-1 [inline] kasan_check_range+0x2b0/0x2c0 mm/kasan/generic.c:189 __asan_memcpy+0x29/0x70 mm/kasan/shadow.c:105 ext4_read_inline_data+0x18f/0x280 fs/ext4/inline.c:214 ext4_inlinedir_to_tree+0x2db/0xac0 fs/ext4/inline.c:1302 ext4_htree_fill_tree+0x3cb/0xef0 fs/ext4/namei.c:1179 ext4_dx_readdir fs/ext4/dir.c:601 [inline] ext4_readdir+0x233a/0x2d10 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+0x8f/0x250 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f9b1c4ac013 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:00007ffd0cc8c828 EFLAGS: 00000293 ORIG_RAX: 00000000000000d9 RAX: ffffffffffffffda RBX: 0000555555a07520 RCX: 00007f9b1c4ac013 RDX: 0000000000008000 RSI: 0000555555a07520 RDI: 0000000000000006 RBP: 0000555555a074f4 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000001000 R11: 0000000000000293 R12: ffffffffffffffa8 R13: 0000000000000016 R14: 0000555555a074f0 R15: 00007ffd0cc8fbc0 The buggy address belongs to the physical page: page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x2e4 pfn:0x12c174 flags: 0x200000000000000(node=0|zone=2) raw: 0200000000000000 ffffea0004b030c8 ffffea0004b05dc8 0000000000000000 raw: 00000000000002e4 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 1461, tgid 1461 (syz-executor), ts 67253527020, free_ts 67347805221 set_page_owner include/linux/page_owner.h:32 [inline] post_alloc_hook+0x168/0x1a0 mm/page_alloc.c:1704 prep_new_page mm/page_alloc.c:1712 [inline] get_page_from_freelist+0x2c22/0x2de0 mm/page_alloc.c:3669 __alloc_frozen_pages_noprof+0x26b/0x460 mm/page_alloc.c:4959 alloc_pages_mpol+0xcb/0x270 mm/mempolicy.c:2419 folio_alloc_mpol_noprof mm/mempolicy.c:2438 [inline] vma_alloc_folio_noprof+0x288/0x400 mm/mempolicy.c:2473 folio_prealloc+0x24/0xf0 mm/memory.c:-1 wp_page_copy mm/memory.c:3569 [inline] do_wp_page+0xb0d/0x2ec0 mm/memory.c:4030 handle_pte_fault mm/memory.c:6085 [inline] __handle_mm_fault mm/memory.c:6212 [inline] handle_mm_fault+0x851/0x2310 mm/memory.c:6381 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:623 page last free pid 1461 tgid 1461 stack trace: reset_page_owner include/linux/page_owner.h:25 [inline] free_pages_prepare mm/page_alloc.c:1248 [inline] free_unref_folios+0xb30/0x1290 mm/page_alloc.c:2763 folios_put_refs+0x319/0x400 mm/swap.c:992 free_pages_and_swap_cache+0x20d/0x3c0 mm/swap_state.c:264 __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+0x382/0x850 mm/mmap.c:1297 __mmput+0x62/0x290 kernel/fork.c:1121 exit_mm+0x11b/0x1b0 kernel/exit.c:581 do_exit+0x506/0x1d40 kernel/exit.c:952 do_group_exit+0x1b1/0x280 kernel/exit.c:1105 get_signal+0xd77/0xeb0 kernel/signal.c:3034 arch_do_signal_or_restart+0x95/0x5b0 arch/x86/kernel/signal.c:337 exit_to_user_mode_loop+0x70/0xd0 kernel/entry/common.c:111 exit_to_user_mode_prepare include/linux/entry-common.h:330 [inline] syscall_exit_to_user_mode_work include/linux/entry-common.h:414 [inline] syscall_exit_to_user_mode include/linux/entry-common.h:449 [inline] do_syscall_64+0x181/0x250 arch/x86/entry/syscall_64.c:100 entry_SYSCALL_64_after_hwframe+0x77/0x7f Memory state around the buggy address: ffff88812c174b00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff88812c174b80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >ffff88812c174c00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ^ ffff88812c174c80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff88812c174d00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ==================================================================