ci2 starts bisection 2026-10-02 05:31:03.233686317 +0000 UTC m=+15131.431885009 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: 0a5c9b73559978094bfa951eabf7309a8ff2f30186545f750f035cf344702f78 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-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: 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 run #10: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #11: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #12: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #13: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #14: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data run #15: crashed: KASAN: slab-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: use-after-free 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] 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 d1cfde2d5d15be14123bdd1689162bd27f995a90 gcc compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8 kernel signature: 8ef5eb87bcd6e642327b23a2ebb2c127c15bec3520d0ea45a02fc626c5997eb3 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: 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: 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-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] the bug reproduces without the instrumentation disabling configs for [atomic_sleep hang memleak ubsan bug_or_warning locking], 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 [locking atomic_sleep hang memleak ubsan bug_or_warning], 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: 82edbc1aa27c399ad9ea11ce9c1f956cffb3ba5ee33244152d89a2b133a140df run #0: crashed: KASAN: slab-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: slab-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: slab-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: 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-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 [locking atomic_sleep hang memleak ubsan bug_or_warning], 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: 81cf871569c2a278072cd2948f3259ba06ad910669aafd4a8d1b1f58ea52abd5 run #0: crashed: KASAN: 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: 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-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: 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: 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 [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: c35586dafecad61ff1c2220aaa7e1cedd0c8615080f8fbe1a1514e0b4b61ccf6 run #0: crashed: KASAN: 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: 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: 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: 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 4/5 disabling configs for [locking atomic_sleep hang memleak ubsan bug_or_warning], 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: 7bb6bca494ef0a6654c4a0b3b893d1ccd832fed0f34e37c6adbdbf8eea62ffba 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: slab-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: 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: 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-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: 81e40a214e189d9e18e5eca82a3c698465ff35f2266f3054679d56cfbef80337 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: 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: 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] the chunk can be dropped disabling configs for [atomic_sleep hang memleak ubsan bug_or_warning locking], they are not needed testing current HEAD 79643295eba17affbd16ca97f3ef04c90266b28c testing commit 79643295eba17affbd16ca97f3ef04c90266b28c gcc compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8 kernel signature: f12a3bf9bb8bcdabd8957c9f1e3b892d9575808f0daa2b8676517c1d5b6c5503 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-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: 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-use-after-free Read in ext4_read_inline_data, types: [KASAN-USE-AFTER-FREE-READ KASAN-READ] crash still not fixed/happens on the oldest tested release revisions tested: 8, total time: 2h29m48.078825395s (build: 1h1m33.834643851s, test: 1h18m8.129913444s) crash still not fixed or there were kernel test errors commit msg: Linux 6.6.157 crash: KASAN: slab-use-after-free 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-use-after-free in ext4_read_inline_data+0x17f/0x260 fs/ext4/inline.c:209 Read of size 68 at addr ffff888118630c80 by task syz.3.17/2940 CPU: 1 PID: 2940 Comm: syz.3.17 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/16/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:2460 ext4_mkdir+0x3fe/0x8d0 fs/ext4/namei.c:3083 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:0x7f11b186bcc7 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:00007f11b16cee58 EFLAGS: 00000246 ORIG_RAX: 0000000000000102 RAX: ffffffffffffffda RBX: 00007f11b16ceee0 RCX: 00007f11b186bcc7 RDX: 00000000000001ff RSI: 0000200000000080 RDI: 00000000ffffff9c RBP: 0000200000000140 R08: 0000200000000080 R09: 0000000000000000 R10: 0000200000000140 R11: 0000000000000246 R12: 0000200000000080 R13: 00007f11b16ceea0 R14: 0000000000000000 R15: 0000000000000000 Allocated by task 2830: 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] kzalloc include/linux/slab.h:721 [inline] tomoyo_encode2 security/tomoyo/realpath.c:45 [inline] tomoyo_encode+0x186/0x460 security/tomoyo/realpath.c:80 tomoyo_realpath_from_path+0x513/0x550 security/tomoyo/realpath.c:283 tomoyo_realpath_nofollow+0x9f/0xf0 security/tomoyo/realpath.c:304 tomoyo_find_next_domain+0x26f/0x1970 security/tomoyo/domain.c:726 tomoyo_bprm_check_security+0xfe/0x130 security/tomoyo/tomoyo.c:101 security_bprm_check+0x27/0x70 security/security.c:1140 search_binary_handler fs/exec.c:1763 [inline] exec_binprm fs/exec.c:1817 [inline] bprm_execve+0x71d/0x1160 fs/exec.c:1892 kernel_execve+0x50b/0x610 fs/exec.c:2058 call_usermodehelper_exec_async+0x1d8/0x2e0 kernel/umh.c:110 ret_from_fork+0x2f/0x60 arch/x86/kernel/process.c:152 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293 Freed by task 2830: 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_find_next_domain+0xcbf/0x1970 security/tomoyo/domain.c:878 tomoyo_bprm_check_security+0xfe/0x130 security/tomoyo/tomoyo.c:101 security_bprm_check+0x27/0x70 security/security.c:1140 search_binary_handler fs/exec.c:1763 [inline] exec_binprm fs/exec.c:1817 [inline] bprm_execve+0x71d/0x1160 fs/exec.c:1892 kernel_execve+0x50b/0x610 fs/exec.c:2058 call_usermodehelper_exec_async+0x1d8/0x2e0 kernel/umh.c:110 ret_from_fork+0x2f/0x60 arch/x86/kernel/process.c:152 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293 The buggy address belongs to the object at ffff888118630c80 which belongs to the cache kmalloc-32 of size 32 The buggy address is located 0 bytes inside of freed 32-byte region [ffff888118630c80, ffff888118630ca0) The buggy address belongs to the physical page: page:ffffea0004618c00 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x118630 anon flags: 0x200000000000800(slab|node=0|zone=2) page_type: 0xffffffff() raw: 0200000000000800 ffff888100041500 ffffea0004618f80 dead000000000003 raw: 0000000000000000 0000000000400040 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected page_owner tracks the page as allocated page last allocated via order 0, migratetype Unmovable, gfp_mask 0x12c40(GFP_NOFS|__GFP_NOWARN|__GFP_NORETRY), pid 785, tgid 785 (udevd), ts 5315338173, free_ts 0 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] kzalloc include/linux/slab.h:721 [inline] tomoyo_encode2 security/tomoyo/realpath.c:45 [inline] tomoyo_encode+0x186/0x460 security/tomoyo/realpath.c:80 tomoyo_realpath_from_path+0x513/0x550 security/tomoyo/realpath.c:283 tomoyo_init_log+0xf36/0x1cc0 security/tomoyo/audit.c:263 tomoyo_supervisor+0x2fa/0xe70 security/tomoyo/common.c:2089 tomoyo_audit_env_log security/tomoyo/environ.c:36 [inline] tomoyo_env_perm+0x107/0x1d0 security/tomoyo/environ.c:63 tomoyo_environ security/tomoyo/domain.c:672 [inline] tomoyo_find_next_domain+0x1051/0x1970 security/tomoyo/domain.c:881 tomoyo_bprm_check_security+0xfe/0x130 security/tomoyo/tomoyo.c:101 security_bprm_check+0x27/0x70 security/security.c:1140 page_owner free stack trace missing Memory state around the buggy address: ffff888118630b80: fa fb fb fb fc fc fc fc fa fb fb fb fc fc fc fc ffff888118630c00: fa fb fb fb fc fc fc fc fa fb fb fb fc fc fc fc >ffff888118630c80: fa fb fb fb fc fc fc fc fa fb fb fb fc fc fc fc ^ ffff888118630d00: 00 00 00 00 fc fc fc fc fa fb fb fb fc fc fc fc ffff888118630d80: fa fb fb fb fc fc fc fc fa fb fb fb fc fc fc fc ==================================================================