ci2 starts bisection 2025-09-02 01:28:44.529279482 +0000 UTC m=+270150.165513849 bisecting fixing commit since 910bfc26d16d07df5a2bfcbc63f0aa9d1397e2ef building syzkaller on 46eb10b79c61c4032281212d862c913683ab32a0 ensuring issue is reproducible on original commit 910bfc26d16d07df5a2bfcbc63f0aa9d1397e2ef testing commit 910bfc26d16d07df5a2bfcbc63f0aa9d1397e2ef gcc compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 kernel signature: 19bde8b40bc262447748ef266ce885e89dc37af010557b0d8b5e458ed909c4e4 run #0: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_dir run #1: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #2: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_dir run #3: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_dir run #4: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_dir run #5: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_dir run #6: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #7: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_dir run #8: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #9: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_dir run #10: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_dir run #11: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_dir run #12: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #13: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_dir run #14: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_dir run #15: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_dir run #16: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_dir run #17: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_dir run #18: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_dir run #19: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_dir representative crash: KASAN: slab-use-after-free Read in ext4_read_inline_dir, types: [KASAN-USE-AFTER-FREE-READ KASAN-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 910bfc26d16d07df5a2bfcbc63f0aa9d1397e2ef gcc compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 kernel signature: 426b77cef3d069045a823ba9ad5b4125bc77e99804cd5c7b8eede2f40f64813f run #0: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_dir run #1: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_dir run #2: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_dir run #3: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_dir run #4: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_dir run #5: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_dir run #6: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_dir run #7: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_dir run #8: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_dir run #9: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_dir representative crash: KASAN: slab-use-after-free Read in ext4_read_inline_dir, types: [KASAN-USE-AFTER-FREE-READ KASAN-READ] the bug reproduces without the instrumentation disabling configs for [hang memleak ubsan bug_or_warning locking atomic_sleep], they are not needed kconfig minimization: base=4092 full=8128 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 [atomic_sleep hang memleak ubsan bug_or_warning locking], they are not needed testing commit 910bfc26d16d07df5a2bfcbc63f0aa9d1397e2ef gcc compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 kernel signature: 9543fb07d0a6c981c5d1e0f963913968cc2eb7c8f9524e9dcc019114d6b7053e run #0: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #1: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #2: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #3: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #4: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #5: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #6: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #7: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #8: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #9: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data representative crash: KASAN: slab-use-after-free Read in ext4_read_inline_data, types: [KASAN-USE-AFTER-FREE-READ KASAN-READ] the chunk can be dropped testing without sub-chunk 2/5 disabling configs for [locking atomic_sleep hang memleak ubsan bug_or_warning], they are not needed testing commit 910bfc26d16d07df5a2bfcbc63f0aa9d1397e2ef gcc compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 kernel signature: bb42899cf21477a3068edbc95408b0f9c55d77fad0d193dfd9971816405f9741 run #0: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #1: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #2: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #3: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #4: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #5: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #6: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #7: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #8: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #9: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data representative crash: KASAN: slab-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 [hang memleak ubsan bug_or_warning locking atomic_sleep], they are not needed testing commit 910bfc26d16d07df5a2bfcbc63f0aa9d1397e2ef gcc compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 kernel signature: c9d1ac6f6ad8c04f72719d5a2104c56bb47d07408e0d8e15d3637b2ea3fa6fad run #0: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #1: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #2: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #3: crashed: KASAN: slab-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: slab-out-of-bounds Read in ext4_read_inline_data run #6: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #7: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #8: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #9: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data representative crash: KASAN: slab-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 910bfc26d16d07df5a2bfcbc63f0aa9d1397e2ef gcc compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 kernel signature: 17ea85392fc6e2740c7318fc4bab8b6c6b58e642b99db12fea68622d0e6bb635 run #0: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #1: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #2: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #3: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #4: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #5: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #6: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #7: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #8: crashed: KASAN: slab-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: slab-out-of-bounds Read in ext4_read_inline_data, types: [KASAN-READ KASAN-USE-AFTER-FREE-READ] the chunk can be dropped testing without sub-chunk 5/5 disabling configs for [hang memleak ubsan bug_or_warning locking atomic_sleep], they are not needed testing commit 910bfc26d16d07df5a2bfcbc63f0aa9d1397e2ef gcc compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 kernel signature: df5f0e0ba0c1c823f9b5a21c853601ac1c54538a476c551df80b334b57657a9d run #0: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #1: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #2: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #3: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #4: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #5: crashed: KASAN: slab-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: slab-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-use-after-free Read in ext4_read_inline_data representative crash: KASAN: slab-use-after-free Read in ext4_read_inline_data, types: [KASAN-USE-AFTER-FREE-READ KASAN-READ] the chunk can be dropped disabling configs for [hang memleak ubsan bug_or_warning locking atomic_sleep], they are not needed testing current HEAD b320789d6883cc00ac78ce83bccbfe7ed58afcf0 testing commit b320789d6883cc00ac78ce83bccbfe7ed58afcf0 gcc compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 kernel signature: 719360cf240627039ddadbd28cdd5f121ca49d3c966e83925ed1b461b82d2dd4 run #0: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #1: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #2: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #3: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #4: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #5: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #6: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #7: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #8: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #9: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data representative crash: KASAN: slab-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: 1h56m20.643070092s (build: 1h7m19.08119793s, test: 41m57.143123469s) crash still not fixed or there were kernel test errors commit msg: Linux 6.17-rc4 crash: KASAN: slab-use-after-free Read in ext4_read_inline_data EXT4-fs error (device loop0): ext4_readdir:264: inode #2: block 16: comm syz-executor: path /0/bus: bad entry in directory: rec_len is smaller than minimal - offset=980, inode=0, rec_len=0, size=1024 fake=0 ================================================================== BUG: KASAN: slab-use-after-free in ext4_read_inline_data+0x18f/0x280 fs/ext4/inline.c:214 Read of size 68 at addr ffff88812573a51a by task syz-executor/2374 CPU: 1 UID: 0 PID: 2374 Comm: syz-executor Not tainted syzkaller #0 PREEMPT(none) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/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/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_read_inline_dir+0x2cd/0x940 fs/ext4/inline.c:1395 ext4_readdir+0x252/0x2d10 fs/ext4/dir.c:162 iterate_dir+0x1a7/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:0x7fcdf9399333 Code: c1 66 0f 1f 44 00 00 48 83 c4 08 48 89 ef 5b 5d e9 02 45 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:00007fff58777548 EFLAGS: 00000293 ORIG_RAX: 00000000000000d9 RAX: ffffffffffffffda RBX: 0000555592838520 RCX: 00007fcdf9399333 RDX: 0000000000008000 RSI: 0000555592838520 RDI: 0000000000000006 RBP: 00005555928384f4 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000001000 R11: 0000000000000293 R12: ffffffffffffffa8 R13: 0000000000000016 R14: 00005555928384f0 R15: 00007fff5877a8e0 Allocated by task 2410: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3e/0x80 mm/kasan/common.c:68 unpoison_slab_object mm/kasan/common.c:330 [inline] __kasan_slab_alloc+0x6c/0x80 mm/kasan/common.c:356 kasan_slab_alloc include/linux/kasan.h:250 [inline] slab_post_alloc_hook mm/slub.c:4180 [inline] slab_alloc_node mm/slub.c:4229 [inline] kmem_cache_alloc_noprof+0x1b1/0x400 mm/slub.c:4236 vm_area_dup+0x22/0x490 mm/vma_init.c:122 __split_vma+0x101/0x7d0 mm/vma.c:515 split_vma mm/vma.c:598 [inline] vma_modify+0x13d1/0x1950 mm/vma.c:1631 vma_modify_flags+0x1c2/0x210 mm/vma.c:1649 mprotect_fixup+0x2bd/0x7c0 mm/mprotect.c:816 do_mprotect_pkey+0x5d8/0x900 mm/mprotect.c:990 __do_sys_mprotect mm/mprotect.c:1011 [inline] __se_sys_mprotect mm/mprotect.c:1008 [inline] __x64_sys_mprotect+0x7b/0x90 mm/mprotect.c:1008 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 Freed by task 15: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3e/0x80 mm/kasan/common.c:68 kasan_save_free_info+0x46/0x50 mm/kasan/generic.c:576 poison_slab_object mm/kasan/common.c:243 [inline] __kasan_slab_free+0x5b/0x80 mm/kasan/common.c:275 kasan_slab_free include/linux/kasan.h:233 [inline] slab_free_hook mm/slub.c:2417 [inline] slab_free_after_rcu_debug+0x131/0x290 mm/slub.c:4730 rcu_do_batch kernel/rcu/tree.c:2605 [inline] rcu_core+0xbe2/0x1570 kernel/rcu/tree.c:2861 handle_softirqs+0x19a/0x500 kernel/softirq.c:579 run_ksoftirqd+0x28/0x40 kernel/softirq.c:968 smpboot_thread_fn+0x3f7/0x7d0 kernel/smpboot.c:160 kthread+0x59b/0x690 kernel/kthread.c:463 ret_from_fork+0x136/0x2d0 arch/x86/kernel/process.c:148 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 Last potentially related work creation: kasan_save_stack+0x3e/0x60 mm/kasan/common.c:47 kasan_record_aux_stack+0xbd/0xd0 mm/kasan/generic.c:548 slab_free_hook mm/slub.c:2378 [inline] slab_free mm/slub.c:4680 [inline] kmem_cache_free+0x2b5/0x460 mm/slub.c:4782 exit_mmap+0x430/0x850 mm/mmap.c:1305 __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 The buggy address belongs to the object at ffff88812573a500 which belongs to the cache vm_area_struct of size 256 The buggy address is located 26 bytes inside of freed 256-byte region [ffff88812573a500, ffff88812573a600) The buggy address belongs to the physical page: page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x12573a memcg:ffff888126a62a01 flags: 0x200000000000000(node=0|zone=2) page_type: f5(slab) raw: 0200000000000000 ffff888100ec3b40 dead000000000122 0000000000000000 raw: 0000000000000000 00000000000c000c 00000000f5000000 ffff888126a62a01 page dumped because: kasan: bad access detected page_owner tracks the page as allocated page last allocated via order 0, migratetype Unmovable, gfp_mask 0x52cc0(GFP_KERNEL|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP), pid 2410, tgid 2410 (modprobe), ts 76644156273, free_ts 76578416457 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 alloc_slab_page mm/slub.c:2487 [inline] allocate_slab+0x8a/0x320 mm/slub.c:2655 new_slab mm/slub.c:2709 [inline] ___slab_alloc+0x9c6/0x10a0 mm/slub.c:3891 __slab_alloc mm/slub.c:3981 [inline] __slab_alloc_node mm/slub.c:4056 [inline] slab_alloc_node mm/slub.c:4217 [inline] kmem_cache_alloc_noprof+0x26e/0x400 mm/slub.c:4236 vm_area_alloc+0x1f/0x130 mm/vma_init.c:31 __mmap_new_vma mm/vma.c:2461 [inline] __mmap_region mm/vma.c:2669 [inline] mmap_region+0xcf6/0x1b90 mm/vma.c:2739 do_mmap+0x930/0xc30 mm/mmap.c:558 vm_mmap_pgoff+0x1c0/0x370 mm/util.c:580 ksys_mmap_pgoff+0x2be/0x3f0 mm/mmap.c:604 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 page last free pid 11 tgid 11 stack trace: reset_page_owner include/linux/page_owner.h:25 [inline] free_pages_prepare mm/page_alloc.c:1395 [inline] __free_frozen_pages+0x9e7/0xb40 mm/page_alloc.c:2895 vfree+0x17d/0x2b0 mm/vmalloc.c:3434 delayed_vfree_work+0x3c/0x70 mm/vmalloc.c:3353 process_one_work kernel/workqueue.c:3236 [inline] process_scheduled_works+0x995/0x12d0 kernel/workqueue.c:3319 worker_thread+0x850/0xc60 kernel/workqueue.c:3400 kthread+0x59b/0x690 kernel/kthread.c:463 ret_from_fork+0x136/0x2d0 arch/x86/kernel/process.c:148 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 Memory state around the buggy address: ffff88812573a400: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff88812573a480: fb fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc >ffff88812573a500: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ^ ffff88812573a580: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff88812573a600: fc fc fc fc fc fc fc fc fa fb fb fb fb fb fb fb ==================================================================