ci2 starts bisection 2025-08-17 09:27:36.910378423 +0000 UTC m=+198474.462854985
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: 9034a3854bc96794f2da5b9bb448fb3487a0d17ed830d9b106ea4a45c071aa4f
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.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
kernel signature: bc628fe3d1c2e572ce2a93ed898b57c479927a4125332fe8c9060e64cc3db626
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=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.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
kernel signature: 1db15126d3c125de82233c04d2855de96c6937c32633e8644b03e88dc6daf77f
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: BUG: unable to handle kernel paging request 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-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: db398ee386ed6ccae1a63f5538f6bb923141206ee2860211c9123c260daf1d92
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 [bug_or_warning locking atomic_sleep hang memleak ubsan], 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: dc2374fb5e422b892dfad5ab3d3c0465e8d81ec01d400485575d993ed1d038f6
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 [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: 51ab4b6f74fcc823badbd442d6a159b33719308118ed968a6af3901c2b8b0623
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 [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: 3ffaf66e0a687cef739905700583063dccdc05851028daf3300924e310ee3945
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 99bade344cfa1577c6dd658e10a3d64b119bddf4
testing commit 99bade344cfa1577c6dd658e10a3d64b119bddf4 gcc
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
kernel signature: 86df93c6cd727a89bb029b68de4f429b6ed6e8ec52370976ffcf92aa7ca005b3
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: 2h9m57.441447143s (build: 1h26m7.367822702s, test: 36m48.689031283s)
crash still not fixed or there were kernel test errors
commit msg: Merge tag 'rust-fixes-6.17' of git://git.kernel.org/pub/scm/linux/kernel/git/ojeda/linux
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 ffff88812bbb7c05 by task syz-executor/1926

CPU: 1 UID: 0 PID: 1926 Comm: syz-executor Not tainted 6.17.0-rc1-syzkaller #0 PREEMPT(none) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/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:0x7faeaa91c013
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:00007ffc83b2de48 EFLAGS: 00000293 ORIG_RAX: 00000000000000d9
RAX: ffffffffffffffda RBX: 000055556957a520 RCX: 00007faeaa91c013
RDX: 0000000000008000 RSI: 000055556957a520 RDI: 0000000000000006
RBP: 000055556957a4f4 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000001000 R11: 0000000000000293 R12: ffffffffffffffa8
R13: 0000000000000016 R14: 000055556957a4f0 R15: 00007ffc83b311e0
 </TASK>

The buggy address belongs to the physical page:
page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x1ce pfn:0x12bbb7
flags: 0x200000000000000(node=0|zone=2)
raw: 0200000000000000 ffffea0004b042c8 ffffea0004aeee88 0000000000000000
raw: 00000000000001ce 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 1920, tgid 1920 (modprobe), ts 65815568990, free_ts 65820275228
 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 1920 tgid 1920 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:997
 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:1130
 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:
 ffff88812bbb7b00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff88812bbb7b80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>ffff88812bbb7c00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
                   ^
 ffff88812bbb7c80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff88812bbb7d00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================