ci2 starts bisection 2025-09-22 03:27:08.537901782 +0000 UTC m=+235496.940022906
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: f37f6a66751983b126d62e7f718670efec2c8eebac035cb74efd3905098a5773
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 [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: 5f75a5e8ea8af53a450b8c408fd41f8bcd09156a3a81b35eca56fc2a586ac7c5
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=4092 full=8129 leaves diff=2141
split chunks (needed=false): <2141>
split chunk #0 of len 2141 into 5 parts
testing without sub-chunk 1/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: 5c6435b0df106d5fabb8eaa7311d8f2612b065f2ebfe138ae7f71b52fd79954e
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: cd3bbde5d058e18cfacbf8e7713ffb69e8ea153248ec26e607f28bdf33191a0d
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: BUG: unable to handle kernel paging request in ext4_read_inline_data
run #8: crashed: KASAN: slab-out-of-bounds 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-USE-AFTER-FREE-READ]
the chunk can be dropped
testing without sub-chunk 3/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: 807c0b370424bcdadc7bd053ae2ae936cf6acbf0d503e44fa94a13030f27e5a1
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 [atomic_sleep hang memleak ubsan bug_or_warning locking], 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: fa04f97277276d819d38b03add9c772220af6acfed824feac9db86760186997a
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 [atomic_sleep hang memleak ubsan bug_or_warning locking], 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: b3777245b052a63ffbb9f89fd26b57c31b7612a7114045ab114098060df715e6
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 07e27ad16399afcd693be20211b0dfae63e0615f
testing commit 07e27ad16399afcd693be20211b0dfae63e0615f gcc
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
kernel signature: 892a7db41d9797e566a4705bfef2d5bd59a9b216eb5741b8409f9e18f233b90c
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: 1h24m24.326501105s (build: 42m38.378393164s, test: 36m4.213771033s)
crash still not fixed or there were kernel test errors
commit msg: Linux 6.17-rc7
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 ffff88812e106c05 by task syz-executor/1925

CPU: 0 UID: 0 PID: 1925 Comm: syz-executor Not tainted syzkaller #0 PREEMPT(none) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
Call Trace:
 <TASK>
 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
 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+0x2d8/0xab0 fs/ext4/inline.c:1276
 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:0x7f40c5e7c013
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:00007ffc1caddb48 EFLAGS: 00000293 ORIG_RAX: 00000000000000d9
RAX: ffffffffffffffda RBX: 0000555559860520 RCX: 00007f40c5e7c013
RDX: 0000000000008000 RSI: 0000555559860520 RDI: 0000000000000006
RBP: 00005555598604f4 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000001000 R11: 0000000000000293 R12: ffffffffffffffa8
R13: 0000000000000016 R14: 00005555598604f0 R15: 00007ffc1cae0ee0
 </TASK>

The buggy address belongs to the physical page:
page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x55a376b0b pfn:0x12e106
flags: 0x200000000000000(node=0|zone=2)
raw: 0200000000000000 ffffea0004ad8608 ffffea0004b832c8 0000000000000000
raw: 000000055a376b0b 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 787, tgid 787 (udevd), ts 65387019511, free_ts 69009329273
 set_page_owner include/linux/page_owner.h:32 [inline]
 post_alloc_hook+0x168/0x1a0 mm/page_alloc.c:1851
 prep_new_page mm/page_alloc.c:1859 [inline]
 get_page_from_freelist+0x287a/0x2a30 mm/page_alloc.c:3858
 __alloc_frozen_pages_noprof+0x26b/0x460 mm/page_alloc.c:5148
 alloc_pages_mpol+0xcb/0x270 mm/mempolicy.c:2416
 folio_alloc_mpol_noprof mm/mempolicy.c:2435 [inline]
 vma_alloc_folio_noprof+0x288/0x400 mm/mempolicy.c:2470
 folio_prealloc+0x24/0xf0 mm/memory.c:-1
 wp_page_copy mm/memory.c:3552 [inline]
 do_wp_page+0xc71/0x2eb0 mm/memory.c:4013
 handle_pte_fault mm/memory.c:6068 [inline]
 __handle_mm_fault mm/memory.c:6195 [inline]
 handle_mm_fault+0x851/0x2310 mm/memory.c:6364
 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 1462 tgid 1462 stack trace:
 reset_page_owner include/linux/page_owner.h:25 [inline]
 free_pages_prepare mm/page_alloc.c:1395 [inline]
 free_unref_folios+0xd04/0x1330 mm/page_alloc.c:2952
 folios_put_refs+0x319/0x400 mm/swap.c:999
 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:1293
 __mmput+0x62/0x290 kernel/fork.c:1129
 exit_mm+0x11b/0x1b0 kernel/exit.c:582
 do_exit+0x506/0x1d50 kernel/exit.c:949
 do_group_exit+0x1b1/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+0x21f7/0x2200 arch/x86/include/generated/asm/syscalls_64.h:232
 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

Memory state around the buggy address:
 ffff88812e106b00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff88812e106b80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>ffff88812e106c00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
                   ^
 ffff88812e106c80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff88812e106d00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================