ci2 starts bisection 2026-08-24 23:09:11.747684289 +0000 UTC m=+106.671329732 bisecting fixing commit since d1cfde2d5d15be14123bdd1689162bd27f995a90 building syzkaller on 43bfcdb07c3552e4664e1029672054ac0924d543 ensuring issue is reproducible on original commit d1cfde2d5d15be14123bdd1689162bd27f995a90 testing commit d1cfde2d5d15be14123bdd1689162bd27f995a90 gcc compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8 kernel signature: e691caaaff75c53bc9c16bfa19fa869abe810f4e670b65d1345df8c2b89cf7d3 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-use-after-free Read in ext4_read_inline_data run #7: crashed: KASAN: slab-out-of-bounds 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 run #10: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #11: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #12: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #13: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #14: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #15: crashed: KASAN: use-after-free Read in ext4_read_inline_data run #16: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #17: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data run #18: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #19: 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] check whether we can drop unnecessary instrumentation disabling configs for [memleak ubsan bug_or_warning locking atomic_sleep hang], they are not needed testing commit d1cfde2d5d15be14123bdd1689162bd27f995a90 gcc compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8 kernel signature: ffbf4a8fb434a67adad785493cb733d90b4ab830270db9d759a14bb8f3f7ac88 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-out-of-bounds Read in ext4_read_inline_data run #7: crashed: KASAN: 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-out-of-bounds 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 bug reproduces without the instrumentation disabling configs for [hang memleak ubsan bug_or_warning locking atomic_sleep], they are not needed kconfig minimization: base=3913 full=7801 leaves diff=2160 split chunks (needed=false): <2160> split chunk #0 of len 2160 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 d1cfde2d5d15be14123bdd1689162bd27f995a90 gcc compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8 kernel signature: 7abe982235ce26308678b48d58c2845a8f631d2a180713efcb96599e329f16b6 run #0: crashed: KASAN: 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-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-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-out-of-bounds 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 KASAN-READ] the chunk can be dropped testing without sub-chunk 2/5 disabling configs for [ubsan bug_or_warning locking atomic_sleep hang memleak], they are not needed testing commit d1cfde2d5d15be14123bdd1689162bd27f995a90 gcc compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8 kernel signature: 7dd2b9958102dd0976444ce910d34ef44412a97cf5a7890d4d16102cf2957819 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: 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: 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: use-after-free Read in ext4_read_inline_data run #7: crashed: KASAN: slab-out-of-bounds 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: 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 3/5 disabling configs for [memleak ubsan bug_or_warning locking atomic_sleep hang], they are not needed testing commit d1cfde2d5d15be14123bdd1689162bd27f995a90 gcc compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8 kernel signature: 48de522bda11016a9e5e1626c9bd932eacf34507b7a107c3c0bc41856db0f3fa 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-use-after-free 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-out-of-bounds 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] 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 d1cfde2d5d15be14123bdd1689162bd27f995a90 gcc compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8 kernel signature: 33072b94eb95a6e7cfa28e9268f63d9cd6313437942458d3eb39ca124a82568a 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-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-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-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 5/5 disabling configs for [hang memleak ubsan bug_or_warning locking atomic_sleep], they are not needed testing commit d1cfde2d5d15be14123bdd1689162bd27f995a90 gcc compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8 kernel signature: 92725e3466bdf1953f5c8810bdef0c485d3d708102ebadefdfafebd0cddad29a 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-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-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-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-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 [atomic_sleep hang memleak ubsan bug_or_warning locking], they are not needed testing current HEAD dc6160265ffc795a1832bc1424f58291d152c7bb testing commit dc6160265ffc795a1832bc1424f58291d152c7bb gcc compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8 kernel signature: 5dd431bc0501a800e8be293675dae4a1fbc3a967bb7f830f9e9f6a0b94604889 run #0: crashed: KASAN: slab-out-of-bounds 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-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: use-after-free 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] crash still not fixed/happens on the oldest tested release revisions tested: 8, total time: 3h49m39.427483893s (build: 45m4.757872914s, test: 1h7m3.261867875s) crash still not fixed or there were kernel test errors commit msg: Linux 6.6.153 crash: KASAN: slab-out-of-bounds Read in ext4_read_inline_data EXT4-fs: Warning: mounting with data=journal disables delayed allocation, dioread_nolock, O_DIRECT and fast_commit support! EXT4-fs (loop3): encrypted files will use data=ordered instead of data journaling mode EXT4-fs (loop3): 1 truncate cleaned up EXT4-fs (loop3): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: none. ================================================================== BUG: KASAN: slab-out-of-bounds in ext4_read_inline_data+0x17f/0x260 fs/ext4/inline.c:209 Read of size 68 at addr ffff88810e343c80 by task syz.3.17/2945 CPU: 0 PID: 2945 Comm: syz.3.17 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026 Call Trace: dump_stack_lvl+0x12a/0x1b0 lib/dump_stack.c:106 print_address_description mm/kasan/report.c:364 [inline] print_report+0xa8/0x210 mm/kasan/report.c:468 kasan_report+0x117/0x150 mm/kasan/report.c:581 check_region_inline mm/kasan/generic.c:-1 [inline] kasan_check_range+0x241/0x290 mm/kasan/generic.c:187 __asan_memcpy+0x29/0x70 mm/kasan/shadow.c:105 ext4_read_inline_data+0x17f/0x260 fs/ext4/inline.c:209 ext4_convert_inline_data_nolock+0x11f/0x630 fs/ext4/inline.c:1214 ext4_try_add_inline_entry+0x5bb/0x950 fs/ext4/inline.c:1340 ext4_add_entry+0x34a/0x2940 fs/ext4/namei.c:2458 ext4_mkdir+0x3fe/0x8d0 fs/ext4/namei.c:3081 vfs_mkdir+0x210/0x380 fs/namei.c:4168 do_mkdirat+0x19a/0x3b0 fs/namei.c:4191 __do_sys_mkdirat fs/namei.c:4206 [inline] __se_sys_mkdirat fs/namei.c:4204 [inline] __x64_sys_mkdirat+0x84/0x90 fs/namei.c:4204 do_syscall_x64 arch/x86/entry/common.c:46 [inline] do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:76 entry_SYSCALL_64_after_hwframe+0x68/0xd2 RIP: 0033:0x7f10b73ebcc7 Code: 00 66 90 48 89 f2 b9 00 01 00 00 48 89 fe bf 9c ff ff ff e9 db f7 ff ff 66 2e 0f 1f 84 00 00 00 00 00 90 b8 02 01 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f10b724ee58 EFLAGS: 00000246 ORIG_RAX: 0000000000000102 RAX: ffffffffffffffda RBX: 00007f10b724eee0 RCX: 00007f10b73ebcc7 RDX: 00000000000001ff RSI: 0000200000000080 RDI: 00000000ffffff9c RBP: 0000200000000140 R08: 0000200000000080 R09: 0000000000000000 R10: 0000200000000140 R11: 0000000000000246 R12: 0000200000000080 R13: 00007f10b724eea0 R14: 0000000000000000 R15: 0000000000000000 Allocated by task 2612: kasan_save_stack mm/kasan/common.c:46 [inline] kasan_set_track+0x4e/0x70 mm/kasan/common.c:53 ____kasan_kmalloc mm/kasan/common.c:375 [inline] __kasan_kmalloc+0x8f/0xa0 mm/kasan/common.c:384 kasan_kmalloc include/linux/kasan.h:198 [inline] __do_kmalloc_node mm/slab_common.c:1007 [inline] __kmalloc+0xa7/0x1c0 mm/slab_common.c:1020 kmalloc include/linux/slab.h:604 [inline] tomoyo_realpath_from_path+0xf3/0x550 security/tomoyo/realpath.c:251 tomoyo_get_realpath security/tomoyo/file.c:151 [inline] tomoyo_path_perm+0x243/0x520 security/tomoyo/file.c:822 security_inode_getattr+0x7f/0xf0 security/security.c:2190 vfs_getattr fs/stat.c:173 [inline] vfs_fstat fs/stat.c:198 [inline] __do_sys_newfstat fs/stat.c:473 [inline] __se_sys_newfstat+0x10f/0x400 fs/stat.c:470 do_syscall_x64 arch/x86/entry/common.c:46 [inline] do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:76 entry_SYSCALL_64_after_hwframe+0x68/0xd2 Freed by task 2612: kasan_save_stack mm/kasan/common.c:46 [inline] kasan_set_track+0x4e/0x70 mm/kasan/common.c:53 kasan_save_free_info+0x28/0x40 mm/kasan/generic.c:522 ____kasan_slab_free+0x126/0x1f0 mm/kasan/common.c:237 kasan_slab_free include/linux/kasan.h:164 [inline] slab_free_hook mm/slub.c:1811 [inline] slab_free_freelist_hook+0x130/0x1a0 mm/slub.c:1837 slab_free mm/slub.c:3830 [inline] __kmem_cache_free+0xba/0x1f0 mm/slub.c:3843 tomoyo_realpath_from_path+0x51e/0x550 security/tomoyo/realpath.c:286 tomoyo_get_realpath security/tomoyo/file.c:151 [inline] tomoyo_path_perm+0x243/0x520 security/tomoyo/file.c:822 security_inode_getattr+0x7f/0xf0 security/security.c:2190 vfs_getattr fs/stat.c:173 [inline] vfs_fstat fs/stat.c:198 [inline] __do_sys_newfstat fs/stat.c:473 [inline] __se_sys_newfstat+0x10f/0x400 fs/stat.c:470 do_syscall_x64 arch/x86/entry/common.c:46 [inline] do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:76 entry_SYSCALL_64_after_hwframe+0x68/0xd2 The buggy address belongs to the object at ffff88810e342000 which belongs to the cache kmalloc-4k of size 4096 The buggy address is located 3200 bytes to the right of allocated 4096-byte region [ffff88810e342000, ffff88810e343000) The buggy address belongs to the physical page: page:ffffea000438d000 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x10e340 head:ffffea000438d000 order:3 entire_mapcount:0 nr_pages_mapped:0 pincount:0 flags: 0x200000000000840(slab|head|node=0|zone=2) page_type: 0xffffffff() raw: 0200000000000840 ffff888100042140 dead000000000100 dead000000000122 raw: 0000000000000000 0000000000040004 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected page_owner tracks the page as allocated page last allocated via order 3, migratetype Unmovable, gfp_mask 0x1d2040(__GFP_IO|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_NOMEMALLOC|__GFP_HARDWALL), pid 1769, tgid 1769 (modprobe), ts 34493786510, free_ts 34051328207 set_page_owner include/linux/page_owner.h:31 [inline] post_alloc_hook+0x24d/0x290 mm/page_alloc.c:1582 prep_new_page mm/page_alloc.c:1589 [inline] get_page_from_freelist+0x2120/0x2290 mm/page_alloc.c:3221 __alloc_pages+0x1f0/0x430 mm/page_alloc.c:4501 alloc_slab_page+0x5d/0x180 mm/slub.c:1881 allocate_slab mm/slub.c:2028 [inline] new_slab+0x70/0x250 mm/slub.c:2081 ___slab_alloc+0xa32/0xee0 mm/slub.c:3253 __slab_alloc mm/slub.c:3339 [inline] __slab_alloc_node mm/slub.c:3392 [inline] slab_alloc_node mm/slub.c:3485 [inline] __kmem_cache_alloc_node+0x118/0x230 mm/slub.c:3534 __do_kmalloc_node mm/slab_common.c:1006 [inline] __kmalloc+0x97/0x1c0 mm/slab_common.c:1020 kmalloc include/linux/slab.h:604 [inline] tomoyo_realpath_from_path+0xf3/0x550 security/tomoyo/realpath.c:251 tomoyo_get_realpath security/tomoyo/file.c:151 [inline] tomoyo_check_open_permission+0x20b/0x5e0 security/tomoyo/file.c:771 security_file_open+0x27/0x90 security/security.c:2968 do_dentry_open+0x2b4/0xf70 fs/open.c:916 do_open fs/namei.c:3683 [inline] path_openat+0x2163/0x27a0 fs/namei.c:3844 do_filp_open+0x1e1/0x3d0 fs/namei.c:3871 do_sys_openat2+0xfc/0x180 fs/open.c:1422 do_sys_open fs/open.c:1437 [inline] __do_sys_openat fs/open.c:1453 [inline] __se_sys_openat fs/open.c:1448 [inline] __x64_sys_openat+0xf4/0x120 fs/open.c:1448 page last free stack trace: reset_page_owner include/linux/page_owner.h:24 [inline] free_pages_prepare mm/page_alloc.c:1182 [inline] free_unref_page_prepare+0x79d/0x8f0 mm/page_alloc.c:2366 free_unref_page+0x32/0x230 mm/page_alloc.c:2459 __slab_free+0x2d4/0x370 mm/slub.c:3736 qlink_free mm/kasan/quarantine.c:166 [inline] qlist_free_all+0x75/0xd0 mm/kasan/quarantine.c:185 kasan_quarantine_reduce+0x143/0x160 mm/kasan/quarantine.c:292 __kasan_slab_alloc+0x22/0x80 mm/kasan/common.c:306 kasan_slab_alloc include/linux/kasan.h:188 [inline] slab_post_alloc_hook+0x66/0x430 mm/slab.h:770 slab_alloc_node mm/slub.c:3495 [inline] slab_alloc mm/slub.c:3503 [inline] __kmem_cache_alloc_lru mm/slub.c:3510 [inline] kmem_cache_alloc+0x174/0x280 mm/slub.c:3519 prepare_creds+0x27/0x410 kernel/cred.c:207 copy_creds+0x188/0x6e0 kernel/cred.c:308 copy_process+0x679/0x2f10 kernel/fork.c:2373 kernel_clone+0x1bd/0x6e0 kernel/fork.c:2919 user_mode_thread+0x10c/0x170 kernel/fork.c:2997 call_usermodehelper_exec_sync kernel/umh.c:133 [inline] call_usermodehelper_exec_work+0x74/0x1c0 kernel/umh.c:164 process_one_work kernel/workqueue.c:2657 [inline] process_scheduled_works+0x8d0/0x11e0 kernel/workqueue.c:2734 worker_thread+0x803/0xc30 kernel/workqueue.c:2815 Memory state around the buggy address: ffff88810e343b80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ffff88810e343c00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc >ffff88810e343c80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ^ ffff88810e343d00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ffff88810e343d80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ==================================================================