ci2 starts bisection 2025-07-22 19:46:17.231970459 +0000 UTC m=+20327.864484792 bisecting fixing commit since e2b9748880b939d8d99877b72cc4cc42951d49b6 building syzkaller on d3ccff6372e07c6aabd02b5da419aa6492b5f0ad ensuring issue is reproducible on original commit e2b9748880b939d8d99877b72cc4cc42951d49b6 testing commit e2b9748880b939d8d99877b72cc4cc42951d49b6 gcc compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7 kernel signature: ebc32b1f9489a48ec68a047ccba73b9f6e23f80f6171a3bc995a6a75e7aa4faa all runs: crashed: KASAN: use-after-free Read in ext4_read_inline_dir representative crash: KASAN: use-after-free Read in ext4_read_inline_dir, types: [KASAN-USE-AFTER-FREE-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 e2b9748880b939d8d99877b72cc4cc42951d49b6 gcc compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7 kernel signature: 9fdc683331610f95f8c1e6c9d1469c0b0427b807b9fdae5952fa957ec4e0a0c8 all runs: crashed: KASAN: use-after-free Read in ext4_read_inline_dir representative crash: KASAN: use-after-free Read in ext4_read_inline_dir, 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=5186 full=6548 leaves diff=266 split chunks (needed=false): <266> split chunk #0 of len 266 into 5 parts testing without sub-chunk 1/5 disabling configs for [bug_or_warning locking atomic_sleep hang memleak ubsan], they are not needed testing commit e2b9748880b939d8d99877b72cc4cc42951d49b6 gcc compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7 kernel signature: 2ab16afb8a6c1a133eadc38c84ea5ccd7b8a14796dfecc0844e810335e337b54 run #0: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #1: crashed: KASAN: out-of-bounds Read in ext4_read_inline_dir run #2: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #3: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #4: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #5: crashed: KASAN: 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: use-after-free Read in ext4_read_inline_dir run #8: crashed: KASAN: use-after-free Read in ext4_read_inline_dir run #9: crashed: KASAN: use-after-free Read in ext4_read_inline_dir representative crash: KASAN: use-after-free Read in ext4_read_inline_dir, types: [KASAN-USE-AFTER-FREE-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 e2b9748880b939d8d99877b72cc4cc42951d49b6 gcc compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7 kernel signature: 6215ce7574c52c7961d546f591c7c9d3d7eae970a9c3c0eed39b778ff350ac0d all runs: crashed: KASAN: use-after-free Read in ext4_read_inline_dir representative crash: KASAN: use-after-free Read in ext4_read_inline_dir, 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 e2b9748880b939d8d99877b72cc4cc42951d49b6 gcc compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7 kernel signature: cbbccbc3138e76e1c5e7962c5079c81dd3e54a5d373daa2cce9cd726d7dbe8d7 all runs: crashed: KASAN: use-after-free Read in ext4_read_inline_dir representative crash: KASAN: use-after-free Read in ext4_read_inline_dir, 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 e2b9748880b939d8d99877b72cc4cc42951d49b6 gcc compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7 kernel signature: f81454057139cbfdf9fb1b35036d51ff345a8646eec73e406866b859e3abb60b all runs: crashed: KASAN: use-after-free Read in ext4_read_inline_dir representative crash: KASAN: use-after-free Read in ext4_read_inline_dir, types: [KASAN-USE-AFTER-FREE-READ] the chunk can be dropped testing without sub-chunk 5/5 disabling configs for [bug_or_warning locking atomic_sleep hang memleak ubsan], they are not needed testing commit e2b9748880b939d8d99877b72cc4cc42951d49b6 gcc compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7 failed building e2b9748880b939d8d99877b72cc4cc42951d49b6: ld.lld: error: undefined symbol: wext_proc_init ld.lld: error: undefined symbol: wext_proc_exit ld.lld: error: undefined symbol: wext_handle_ioctl ld.lld: error: undefined symbol: compat_wext_handle_ioctl minimized to 50 configs; suspects: [HID_ZEROPLUS USB_NET_GL620A USB_NET_MCS7830 USB_NET_NET1080 USB_NET_PLUSB USB_NET_RNDIS_HOST USB_NET_SMSC75XX USB_NET_SMSC95XX USB_NET_SR9700 USB_NET_SR9800 USB_NET_ZAURUS USB_OHCI_HCD USB_OHCI_HCD_PCI USB_OHCI_HCD_PLATFORM USB_OTG USB_OTG_FSM USB_PRINTER USB_SERIAL_GENERIC USB_SERIAL_PL2303 USB_STORAGE_ALAUDA USB_STORAGE_CYPRESS_ATACB USB_STORAGE_DATAFAB USB_STORAGE_FREECOM USB_STORAGE_ISD200 USB_STORAGE_JUMPSHOT USB_STORAGE_KARMA USB_STORAGE_ONETOUCH USB_STORAGE_SDDR09 USB_STORAGE_SDDR55 USB_STORAGE_USBAT USB_TRANCEVIBRATOR USB_U_AUDIO USB_U_ETHER USB_U_SERIAL USB_WDM V4L2_ASYNC V4L2_FWNODE VIDEO_CAMERA_SENSOR WLAN WLAN_VENDOR_ATH WLAN_VENDOR_ATMEL WLAN_VENDOR_BROADCOM WLAN_VENDOR_INTERSIL WLAN_VENDOR_MARVELL WLAN_VENDOR_MEDIATEK WLAN_VENDOR_MICROCHIP WLAN_VENDOR_PURELIFI WLAN_VENDOR_RALINK WLAN_VENDOR_REALTEK WLAN_VENDOR_RSI WLAN_VENDOR_SILABS WLAN_VENDOR_ZYDAS X86_X32_ABI ZEROPLUS_FF] disabling configs for [hang memleak ubsan bug_or_warning locking atomic_sleep], they are not needed testing current HEAD de932537be34afdfb9be5a872cd238aadf007476 testing commit de932537be34afdfb9be5a872cd238aadf007476 gcc compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7 kernel signature: e0d4f364ee48b94e74809a684424a66f2eca1e08de0ab40b26104ac3e3d65f85 all runs: crashed: KASAN: use-after-free Read in ext4_read_inline_dir representative crash: KASAN: use-after-free Read in ext4_read_inline_dir, types: [KASAN-USE-AFTER-FREE-READ] crash still not fixed/happens on the oldest tested release revisions tested: 7, total time: 1h34m59.572989832s (build: 1h5m55.766199856s, test: 25m6.96348355s) crash still not fixed or there were kernel test errors commit msg: ANDROID: ABI: Update the symbol list for mtk crash: KASAN: use-after-free Read in ext4_read_inline_dir ================================================================== BUG: KASAN: use-after-free in ext4_read_inline_data fs/ext4/inline.c:210 [inline] BUG: KASAN: use-after-free in ext4_read_inline_dir+0x344/0xbe0 fs/ext4/inline.c:1512 Read of size 68 at addr ffff88812ea67d05 by task syz-executor/474 CPU: 0 PID: 474 Comm: syz-executor Not tainted 6.1.141-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 Call Trace: __dump_stack+0x19/0x1c lib/dump_stack.c:88 dump_stack_lvl+0xa3/0xec lib/dump_stack.c:106 print_address_description+0x71/0x210 mm/kasan/report.c:316 print_report+0x4a/0x60 mm/kasan/report.c:427 kasan_report+0x122/0x150 mm/kasan/report.c:531 check_region_inline mm/kasan/generic.c:-1 [inline] kasan_check_range+0x280/0x290 mm/kasan/generic.c:189 memcpy+0x2d/0x70 mm/kasan/shadow.c:65 ext4_read_inline_data fs/ext4/inline.c:210 [inline] ext4_read_inline_dir+0x344/0xbe0 fs/ext4/inline.c:1512 ext4_readdir+0x256/0x31e0 fs/ext4/dir.c:161 iterate_dir+0x221/0x540 fs/readdir.c:-1 __do_sys_getdents64 fs/readdir.c:369 [inline] __se_sys_getdents64+0xc9/0x190 fs/readdir.c:354 __x64_sys_getdents64+0x76/0x80 fs/readdir.c:354 x64_sys_call+0x15c/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:218 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x68/0xd2 RIP: 0033:0x7f534c1b8693 Code: c1 66 0f 1f 44 00 00 48 83 c4 08 48 89 ef 5b 5d e9 82 3e 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:00007ffe7d111738 EFLAGS: 00000293 ORIG_RAX: 00000000000000d9 RAX: ffffffffffffffda RBX: 00005555892ed520 RCX: 00007f534c1b8693 RDX: 0000000000008000 RSI: 00005555892ed520 RDI: 0000000000000006 RBP: 00005555892ed4f4 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000001000 R11: 0000000000000293 R12: ffffffffffffffa8 R13: 0000000000000016 R14: 00005555892ed4f0 R15: 0000000000000001 The buggy address belongs to the physical page: page:ffffea0004ba99c0 refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x12ea67 flags: 0x4000000000000000(zone=1) raw: 4000000000000000 ffffea0004ba9a08 ffffea0004ba9988 0000000000000000 raw: 0000000000000001 0000000000000000 00000000ffffffff 0000000000000000 page dumped because: kasan: bad access detected page_owner info is not present (never set?) Memory state around the buggy address: ffff88812ea67c00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff88812ea67c80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >ffff88812ea67d00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ^ ffff88812ea67d80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff88812ea67e00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ================================================================== EXT4-fs error (device loop1): ext4_read_inline_dir:1593: inode #12: block 5: comm syz-executor: path /0/file0/file0: bad entry in directory: rec_len % 4 != 0 - offset=24, inode=1633771873, rec_len=24929, size=148 fake=0 EXT4-fs error (device loop1): ext4_read_inline_dir:1593: inode #12: block 5: comm syz-executor: path /0/file0/file0: bad entry in directory: rec_len % 4 != 0 - offset=24, inode=1633771873, rec_len=24929, size=148 fake=0 EXT4-fs error (device loop1): empty_inline_dir:1877: inode #12: block 5: comm syz-executor: bad entry in directory: rec_len % 4 != 0 - offset=4, inode=1633771873, rec_len=24929, size=60 fake=0 EXT4-fs warning (device loop1): empty_inline_dir:1884: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60 EXT4-fs error (device loop1): ext4_read_inline_dir:1593: inode #12: block 5: comm syz-executor: path /0/file0/file0: bad entry in directory: rec_len % 4 != 0 - offset=24, inode=1633771873, rec_len=24929, size=148 fake=0 EXT4-fs error (device loop1): ext4_read_inline_dir:1593: inode #12: block 5: comm syz-executor: path /0/file0/file0: bad entry in directory: rec_len % 4 != 0 - offset=24, inode=1633771873, rec_len=24929, size=148 fake=0 EXT4-fs error (device loop1): empty_inline_dir:1877: inode #12: block 5: comm syz-executor: bad entry in directory: rec_len % 4 != 0 - offset=4, inode=1633771873, rec_len=24929, size=60 fake=0 EXT4-fs warning (device loop1): empty_inline_dir:1884: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60 EXT4-fs error (device loop1): ext4_read_inline_dir:1593: inode #12: block 5: comm syz-executor: path /0/file0/file0: bad entry in directory: rec_len % 4 != 0 - offset=24, inode=1633771873, rec_len=24929, size=148 fake=0 EXT4-fs error (device loop1): ext4_read_inline_dir:1593: inode #12: block 5: comm syz-executor: path /0/file0/file0: bad entry in directory: rec_len % 4 != 0 - offset=24, inode=1633771873, rec_len=24929, size=148 fake=0 EXT4-fs error (device loop1): empty_inline_dir:1877: inode #12: block 5: comm syz-executor: bad entry in directory: rec_len % 4 != 0 - offset=4, inode=1633771873, rec_len=24929, size=60 fake=0 EXT4-fs warning (device loop1): empty_inline_dir:1884: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60 EXT4-fs warning (device loop1): empty_inline_dir:1884: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60 EXT4-fs warning (device loop1): empty_inline_dir:1884: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60 EXT4-fs warning (device loop1): empty_inline_dir:1884: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60 EXT4-fs warning (device loop1): empty_inline_dir:1884: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60 EXT4-fs warning (device loop1): empty_inline_dir:1884: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60 EXT4-fs warning (device loop1): empty_inline_dir:1884: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60 EXT4-fs warning (device loop1): empty_inline_dir:1884: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60 EXT4-fs (loop1): unmounting filesystem.