ci2 starts bisection 2024-10-28 17:45:33.36132555 +0000 UTC m=+10396.470291754 bisecting fixing commit since 8d23314f588a573519ab88c332e94c927f870810 building syzkaller on c7e35043b5a47c5628f796d775fd213c62613c5d ensuring issue is reproducible on original commit 8d23314f588a573519ab88c332e94c927f870810 testing commit 8d23314f588a573519ab88c332e94c927f870810 gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: e9ea502188810288ac4c2307031bed5e08290f37fc132aa1d3ff8ec9be8f1ddd all runs: crashed: KASAN: use-after-free Write in ext4_insert_dentry representative crash: KASAN: use-after-free Write in ext4_insert_dentry, types: [KASAN] check whether we can drop unnecessary instrumentation disabling configs for [ATOMIC_SLEEP HANG LEAK UBSAN BUG LOCKDEP], they are not needed testing commit 8d23314f588a573519ab88c332e94c927f870810 gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: 2b11594479f766d53791ea358ca76531f97b5acf87700ea37f264d5ef2d3651c all runs: crashed: KASAN: use-after-free Write in ext4_insert_dentry representative crash: KASAN: use-after-free Write in ext4_insert_dentry, types: [KASAN] the bug reproduces without the instrumentation disabling configs for [LOCKDEP ATOMIC_SLEEP HANG LEAK UBSAN BUG], they are not needed kconfig minimization: base=4789 full=6020 leaves diff=243 split chunks (needed=false): <243> split chunk #0 of len 243 into 5 parts testing without sub-chunk 1/5 disabling configs for [LOCKDEP ATOMIC_SLEEP HANG LEAK UBSAN BUG], they are not needed testing commit 8d23314f588a573519ab88c332e94c927f870810 gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: f6bdd4eda2fed12a7372a3ca1907f738a4b7c467b81df93127806aff3c9f051a all runs: crashed: KASAN: use-after-free Write in ext4_insert_dentry representative crash: KASAN: use-after-free Write in ext4_insert_dentry, types: [KASAN] the chunk can be dropped testing without sub-chunk 2/5 disabling configs for [HANG LEAK UBSAN BUG LOCKDEP ATOMIC_SLEEP], they are not needed testing commit 8d23314f588a573519ab88c332e94c927f870810 gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: cf4327ae0fd55d3492c83afa9a3561a7a66b55ddae9b558d0804056a2e7535a0 all runs: crashed: KASAN: use-after-free Write in ext4_insert_dentry representative crash: KASAN: use-after-free Write in ext4_insert_dentry, types: [KASAN] the chunk can be dropped testing without sub-chunk 3/5 disabling configs for [HANG LEAK UBSAN BUG LOCKDEP ATOMIC_SLEEP], they are not needed testing commit 8d23314f588a573519ab88c332e94c927f870810 gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: 2ca3c34e1bd9a76f11f1f9937df46ed3e05059ad9072cbb293ed1b5a8ae6db30 all runs: crashed: KASAN: use-after-free Write in ext4_insert_dentry representative crash: KASAN: use-after-free Write in ext4_insert_dentry, types: [KASAN] the chunk can be dropped testing without sub-chunk 4/5 disabling configs for [LOCKDEP ATOMIC_SLEEP HANG LEAK UBSAN BUG], they are not needed testing commit 8d23314f588a573519ab88c332e94c927f870810 gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: e9e4340e0dc35d4cad05d8c58655449741780e5db5706db9362fc019ff3ff00c all runs: crashed: KASAN: use-after-free Write in ext4_insert_dentry representative crash: KASAN: use-after-free Write in ext4_insert_dentry, types: [KASAN] the chunk can be dropped testing without sub-chunk 5/5 disabling configs for [BUG LOCKDEP ATOMIC_SLEEP HANG LEAK UBSAN], they are not needed testing commit 8d23314f588a573519ab88c332e94c927f870810 gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.40 failed building 8d23314f588a573519ab88c332e94c927f870810: net/socket.c:1128: undefined reference to `wext_handle_ioctl' net/socket.c:3397: undefined reference to `compat_wext_handle_ioctl' net/core/net-procfs.c:346: undefined reference to `wext_proc_exit' net/core/net-procfs.c:330: undefined reference to `wext_proc_init' minimized to 47 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 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 X86_X32 ZEROPLUS_FF] disabling configs for [UBSAN BUG LOCKDEP ATOMIC_SLEEP HANG LEAK], they are not needed testing current HEAD e5e5644ea27f86a29c84df744a01ea7de65ef800 testing commit e5e5644ea27f86a29c84df744a01ea7de65ef800 gcc compiler: gcc (GCC) 10.2.1 20210217, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: 48cb8fae0127fc8adeb26679d6b186b02e60db93c06d5250049aa2270f08c928 all runs: crashed: KASAN: use-after-free Write in ext4_insert_dentry representative crash: KASAN: use-after-free Write in ext4_insert_dentry, types: [KASAN] crash still not fixed/happens on the oldest tested release revisions tested: 7, total time: 2h11m27.941324387s (build: 1h21m10.683282155s, test: 44m23.775679298s) crash still not fixed or there were kernel test errors commit msg: Revert "udf: Avoid excessive partition lengths" crash: KASAN: use-after-free Write in ext4_insert_dentry ================================================================== BUG: KASAN: use-after-free in ext4_insert_dentry+0x2d8/0x660 fs/ext4/namei.c:2117 Write of size 254 at addr ffff88811f8a8f0c by task syz.0.15/472 CPU: 1 PID: 472 Comm: syz.0.15 Not tainted 5.10.226-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 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 check_region_inline mm/kasan/generic.c:183 [inline] kasan_check_range+0x148/0x190 mm/kasan/generic.c:189 memcpy+0x3c/0x60 mm/kasan/shadow.c:66 ext4_insert_dentry+0x2d8/0x660 fs/ext4/namei.c:2117 add_dirent_to_buf+0x289/0x690 fs/ext4/namei.c:2161 make_indexed_dir+0xe05/0x1210 fs/ext4/namei.c:2352 ext4_add_entry+0xd94/0x11f0 fs/ext4/namei.c:2458 __ext4_link+0x337/0x4b0 fs/ext4/namei.c:3645 ext4_link+0x1a1/0x240 fs/ext4/namei.c:3686 vfs_link+0x6b2/0xaa0 fs/namei.c:4213 do_linkat+0x329/0x520 fs/namei.c:4281 __do_sys_link fs/namei.c:4310 [inline] __se_sys_link fs/namei.c:4308 [inline] __x64_sys_link+0x5c/0x80 fs/namei.c:4308 do_syscall_64+0x32/0x80 arch/x86/entry/common.c:46 entry_SYSCALL_64_after_hwframe+0x61/0xcb RIP: 0033:0x7f6745865ef9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f67452e7038 EFLAGS: 00000246 ORIG_RAX: 0000000000000056 RAX: ffffffffffffffda RBX: 00007f6745a1df80 RCX: 00007f6745865ef9 RDX: 0000000000000000 RSI: 0000000020000bc0 RDI: 0000000020001240 RBP: 00007f67458d8b76 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007f6745a1df80 R15: 00007ffd0ab73088 The buggy address belongs to the page: page:ffffea00047e2a00 refcount:3 mapcount:0 mapping:ffff888108eab150 index:0x3f pfn:0x11f8a8 aops:def_blk_aops ino:0 flags: 0x400000000000202a(referenced|dirty|active|private) raw: 400000000000202a dead000000000100 dead000000000122 ffff888108eab150 raw: 000000000000003f ffff888108de2dc8 00000003ffffffff ffff888121bba000 page dumped because: kasan: bad access detected page->mem_cgroup:ffff888121bba000 page_owner tracks the page as allocated page last allocated via order 0, migratetype Movable, gfp_mask 0x108c48(GFP_NOFS|__GFP_NOFAIL|__GFP_HARDWALL|__GFP_MOVABLE), pid 472, ts 57349557325, free_ts 56918533043 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/0x23d0 mm/page_alloc.c:5348 __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] __page_cache_alloc include/linux/pagemap.h:290 [inline] pagecache_get_page+0x169/0x6f0 mm/filemap.c:1848 find_or_create_page include/linux/pagemap.h:402 [inline] grow_dev_page fs/buffer.c:976 [inline] grow_buffers fs/buffer.c:1045 [inline] __getblk_slow+0x1ad/0x580 fs/buffer.c:1072 __getblk_gfp+0x3d/0x50 fs/buffer.c:1370 sb_getblk include/linux/buffer_head.h:361 [inline] ext4_getblk+0x1b1/0x5a0 fs/ext4/inode.c:877 ext4_bread+0xc/0x150 fs/ext4/inode.c:922 ext4_append+0x203/0x560 fs/ext4/namei.c:83 make_indexed_dir+0x40b/0x1210 fs/ext4/namei.c:2278 ext4_add_entry+0xd94/0x11f0 fs/ext4/namei.c:2458 __ext4_link+0x337/0x4b0 fs/ext4/namei.c:3645 ext4_link+0x1a1/0x240 fs/ext4/namei.c:3686 vfs_link+0x6b2/0xaa0 fs/namei.c:4213 do_linkat+0x329/0x520 fs/namei.c:4281 __do_sys_link fs/namei.c:4310 [inline] __se_sys_link fs/namei.c:4308 [inline] __x64_sys_link+0x5c/0x80 fs/namei.c:4308 do_syscall_64+0x32/0x80 arch/x86/entry/common.c:46 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 exit_mmap+0x294/0x570 mm/mmap.c:3357 __mmput kernel/fork.c:1153 [inline] mmput kernel/fork.c:1176 [inline] mmput+0x99/0x430 kernel/fork.c:1170 exit_mm kernel/exit.c:539 [inline] do_exit+0x86b/0x2330 kernel/exit.c:850 do_group_exit+0xe6/0x290 kernel/exit.c:985 get_signal+0x353/0x1a10 kernel/signal.c:2790 arch_do_signal_or_restart+0x2ad/0x2510 arch/x86/kernel/signal.c:805 handle_signal_work kernel/entry/common.c:145 [inline] exit_to_user_mode_loop kernel/entry/common.c:169 [inline] exit_to_user_mode_prepare+0xd1/0x120 kernel/entry/common.c:199 syscall_exit_to_user_mode+0x27/0x160 kernel/entry/common.c:274 do_syscall_64+0x3f/0x80 arch/x86/entry/common.c:56 entry_SYSCALL_64_after_hwframe+0x61/0xcb Memory state around the buggy address: ffff88811f8a8f00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff88811f8a8f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffff88811f8a9000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ^ ffff88811f8a9080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff88811f8a9100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ==================================================================