ci2 starts bisection 2026-09-03 11:51:42.697749519 +0000 UTC m=+29201.575374859 bisecting fixing commit since 50b3a256e550e98ff6a49d32e77fb67998707961 building syzkaller on a0c310a3e11cde5f0873c07ded31e667f0a586a0 ensuring issue is reproducible on original commit 50b3a256e550e98ff6a49d32e77fb67998707961 testing commit 50b3a256e550e98ff6a49d32e77fb67998707961 gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.44 kernel signature: 272d5fd07362aca3a8057049ad59e010d1b1ab33dcbe7053b45724429acab773 all runs: crashed: KASAN: use-after-free Read in ext4_get_inode_usage representative crash: KASAN: use-after-free Read in ext4_get_inode_usage, 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 50b3a256e550e98ff6a49d32e77fb67998707961 gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.44 kernel signature: bbd1d9dd866dd7d1ccf9006dbd49e8e65fc791d35c011d10bfcbd7df3f1d4eda all runs: crashed: KASAN: use-after-free Read in ext4_get_inode_usage representative crash: KASAN: use-after-free Read in ext4_get_inode_usage, types: [KASAN-USE-AFTER-FREE-READ] the bug reproduces without the instrumentation disabling configs for [ubsan bug_or_warning locking atomic_sleep hang memleak], they are not needed kconfig minimization: base=4788 full=6024 leaves diff=248 split chunks (needed=false): <248> split chunk #0 of len 248 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 50b3a256e550e98ff6a49d32e77fb67998707961 gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.44 kernel signature: e512a98ed9cdd2476d923a1b54ad2d3671b1f324982489d6d0d837549e51c7f9 all runs: crashed: KASAN: use-after-free Read in ext4_get_inode_usage representative crash: KASAN: use-after-free Read in ext4_get_inode_usage, types: [KASAN-USE-AFTER-FREE-READ] the chunk can be dropped testing without sub-chunk 2/5 disabling configs for [hang memleak ubsan bug_or_warning locking atomic_sleep], they are not needed testing commit 50b3a256e550e98ff6a49d32e77fb67998707961 gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.44 kernel signature: 7c421c7d4b52eaa4760e0e386689e0315b8f3549f6fbe0a102d92f8fbaae7ac7 all runs: crashed: KASAN: use-after-free Read in ext4_get_inode_usage representative crash: KASAN: use-after-free Read in ext4_get_inode_usage, types: [KASAN-USE-AFTER-FREE-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 50b3a256e550e98ff6a49d32e77fb67998707961 gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.44 kernel signature: a34bc8c5582dda614bf05684a43e2e3b65ca0cfd81ab770cc729c50eba7fc264 all runs: crashed: KASAN: use-after-free Read in ext4_get_inode_usage representative crash: KASAN: use-after-free Read in ext4_get_inode_usage, 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 50b3a256e550e98ff6a49d32e77fb67998707961 gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.44 kernel signature: 18db4c59f7b41d7d6ea7c04cfd8e7c5f6bd84089664168dc9718e75133236386 all runs: crashed: KASAN: use-after-free Read in ext4_get_inode_usage representative crash: KASAN: use-after-free Read in ext4_get_inode_usage, types: [KASAN-USE-AFTER-FREE-READ] the chunk can be dropped testing without sub-chunk 5/5 disabling configs for [locking atomic_sleep hang memleak ubsan bug_or_warning], they are not needed testing commit 50b3a256e550e98ff6a49d32e77fb67998707961 gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.44 failed building 50b3a256e550e98ff6a49d32e77fb67998707961: net/socket.c:1129:(.text+0x1307): undefined reference to `wext_handle_ioctl' net/socket.c:3398:(.text+0x17c7): undefined reference to `compat_wext_handle_ioctl' net/core/net-procfs.c:346:(.text+0x33b): undefined reference to `wext_proc_exit' net/core/net-procfs.c:330:(.text+0x4e2): undefined reference to `wext_proc_init' minimized to 48 configs; suspects: [HID_ZEROPLUS USB_NET_CDC_SUBSET USB_NET_CDC_SUBSET_ENABLE USB_NET_DM9601 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 USB_SERIAL_FTDI_SIO 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 USB_XHCI_PCI_RENESAS WLAN WLAN_VENDOR_ATH WLAN_VENDOR_ATMEL WLAN_VENDOR_BROADCOM WLAN_VENDOR_INTERSIL WLAN_VENDOR_MARVELL WLAN_VENDOR_MEDIATEK WLAN_VENDOR_MICROCHIP WLAN_VENDOR_RALINK WLAN_VENDOR_REALTEK WLAN_VENDOR_RSI WLAN_VENDOR_ZYDAS ZEROPLUS_FF] disabling configs for [hang memleak ubsan bug_or_warning locking atomic_sleep], they are not needed testing current HEAD 452567d1985b87b56468536292b8eccd299a6c4b testing commit 452567d1985b87b56468536292b8eccd299a6c4b gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.44 kernel signature: 5b4e23492dbe1c8915427ea4a2fcd65054bce3ae1cf8f820fcc5f7c11df582be all runs: crashed: KASAN: use-after-free Read in ext4_get_inode_usage representative crash: KASAN: use-after-free Read in ext4_get_inode_usage, types: [KASAN-USE-AFTER-FREE-READ] crash still not fixed/happens on the oldest tested release revisions tested: 7, total time: 1h57m10.348132323s (build: 1h0m51.044345881s, test: 49m39.232036688s) crash still not fixed or there were kernel test errors commit msg: Revert "HID: input: read battery capacity from its actual report offset" crash: KASAN: use-after-free Read in ext4_get_inode_usage EXT4-fs (loop2): mounted filesystem without journal. Opts: ,errors=continue EXT4-fs error (device loop2): xattr_find_entry:297: inode #15: comm syz.2.18: corrupted xattr entries ================================================================== BUG: KASAN: use-after-free in ext4_get_inode_usage+0x2c6/0x970 fs/ext4/xattr.c:819 Read of size 4 at addr ffff888129202000 by task syz.2.18/490 CPU: 0 PID: 490 Comm: syz.2.18 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack_lvl+0x81/0xac lib/dump_stack.c:118 print_address_description.constprop.0+0x24/0x160 mm/kasan/report.c:248 __kasan_report mm/kasan/report.c:435 [inline] kasan_report.cold+0x82/0xdb mm/kasan/report.c:452 __asan_report_load4_noabort+0x14/0x20 mm/kasan/report_generic.c:308 ext4_get_inode_usage+0x2c6/0x970 fs/ext4/xattr.c:819 __dquot_transfer+0x1a8/0x1380 fs/quota/dquot.c:2039 dquot_transfer+0x24a/0x3f0 fs/quota/dquot.c:2191 ext4_setattr+0x412/0x2040 fs/ext4/inode.c:5577 notify_change+0x7b0/0xd90 fs/attr.c:410 chown_common+0x2b2/0x4c0 fs/open.c:675 do_fchownat+0xe9/0x160 fs/open.c:705 __do_sys_lchown fs/open.c:730 [inline] __se_sys_lchown fs/open.c:728 [inline] __x64_sys_lchown+0x79/0xb0 fs/open.c:728 do_syscall_64+0x32/0x50 arch/x86/entry/common.c:46 entry_SYSCALL_64_after_hwframe+0x61/0xcb RIP: 0033:0x7f2c16865e59 Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 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:00007f2c166c7028 EFLAGS: 00000246 ORIG_RAX: 000000000000005e RAX: ffffffffffffffda RBX: 00007f2c16aedfa0 RCX: 00007f2c16865e59 RDX: 0000000000000000 RSI: 00000000000000ff RDI: 00002000000004c0 RBP: 00007f2c168fbe6f R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f2c16aee038 R14: 00007f2c16aedfa0 R15: 00007ffd7f083218 The buggy address belongs to the page: page:ffffea0004a48080 refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x129202 flags: 0x4000000000000000() raw: 4000000000000000 ffffea0004a48848 ffffea0004a480c8 0000000000000000 raw: 0000000000000001 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 0x8100dca(GFP_HIGHUSER_MOVABLE|__GFP_ZERO|0x8000000), pid 435, ts 38309462966, free_ts 38311865299 set_page_owner include/linux/page_owner.h:35 [inline] post_alloc_hook mm/page_alloc.c:2456 [inline] prep_new_page mm/page_alloc.c:2462 [inline] get_page_from_freelist+0x1fee/0x2ad0 mm/page_alloc.c:4254 __alloc_pages_nodemask+0x2ae/0x2540 mm/page_alloc.c:5384 __alloc_pages include/linux/gfp.h:544 [inline] __alloc_pages_node include/linux/gfp.h:557 [inline] alloc_pages_node include/linux/gfp.h:571 [inline] alloc_pages include/linux/gfp.h:590 [inline] do_anonymous_page mm/memory.c:3963 [inline] handle_pte_fault+0x16f1/0x3230 mm/memory.c:4795 __handle_mm_fault+0xac7/0xfa0 mm/memory.c:4953 handle_mm_fault+0x1b8/0x6b0 mm/memory.c:5367 do_user_addr_fault+0x562/0xd70 arch/x86/mm/fault.c:1343 handle_page_fault arch/x86/mm/fault.c:1436 [inline] exc_page_fault+0x65/0xc0 arch/x86/mm/fault.c:1492 asm_exc_page_fault+0x1e/0x30 arch/x86/include/asm/idtentry.h:571 page last free stack trace: reset_page_owner include/linux/page_owner.h:28 [inline] free_pages_prepare mm/page_alloc.c:1349 [inline] free_pcp_prepare+0x1a7/0x230 mm/page_alloc.c:1421 free_unref_page_prepare mm/page_alloc.c:3336 [inline] free_unref_page_list+0x18a/0xae0 mm/page_alloc.c:3443 release_pages+0x374/0xb00 mm/swap.c:1103 free_pages_and_swap_cache+0x180/0x1e0 mm/swap_state.c:356 tlb_batch_pages_flush mm/mmu_gather.c:49 [inline] tlb_flush_mmu_free mm/mmu_gather.c:240 [inline] tlb_flush_mmu mm/mmu_gather.c:247 [inline] tlb_finish_mmu+0x129/0x790 mm/mmu_gather.c:326 unmap_region+0x2ee/0x400 mm/mmap.c:2811 __do_munmap+0x495/0x1000 mm/mmap.c:3041 __vm_munmap+0xfb/0x1a0 mm/mmap.c:3094 __do_sys_munmap mm/mmap.c:3120 [inline] __se_sys_munmap mm/mmap.c:3116 [inline] __x64_sys_munmap+0x62/0x80 mm/mmap.c:3116 do_syscall_64+0x32/0x50 arch/x86/entry/common.c:46 entry_SYSCALL_64_after_hwframe+0x61/0xcb Memory state around the buggy address: ffff888129201f00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff888129201f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffff888129202000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ^ ffff888129202080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff888129202100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ==================================================================