ci starts bisection 2023-06-24 02:09:50.44102515 +0000 UTC m=+329256.102511586 bisecting fixing commit since fff5a5e7f528b2ed2c335991399a766c2cf01103 building syzkaller on f94b4a29b579b3de9aab3b41915e3663e6f7094e ensuring issue is reproducible on original commit fff5a5e7f528b2ed2c335991399a766c2cf01103 testing commit fff5a5e7f528b2ed2c335991399a766c2cf01103 gcc compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: f188f4c03574ab68733568139d25ac98ff9d40113882bb95ca226915e2c41bf7 run #0: crashed: KASAN: use-after-free Read in jfs_readdir run #1: crashed: KASAN: use-after-free Read in jfs_readdir run #2: crashed: KASAN: slab-use-after-free Read in jfs_readdir run #3: crashed: KASAN: slab-out-of-bounds Read in jfs_readdir run #4: crashed: KASAN: use-after-free Read in jfs_readdir run #5: crashed: KASAN: slab-out-of-bounds Read in jfs_readdir run #6: crashed: KASAN: slab-out-of-bounds Read in jfs_readdir run #7: crashed: KASAN: use-after-free Read in jfs_readdir run #8: crashed: KASAN: slab-out-of-bounds Read in jfs_readdir run #9: crashed: KASAN: slab-out-of-bounds Read in jfs_readdir run #10: crashed: KASAN: use-after-free Read in jfs_readdir run #11: crashed: KASAN: slab-use-after-free Read in jfs_readdir run #12: crashed: KASAN: slab-out-of-bounds Read in jfs_readdir run #13: crashed: KASAN: slab-use-after-free Read in jfs_readdir run #14: crashed: KASAN: slab-out-of-bounds Read in jfs_readdir run #15: crashed: KASAN: slab-out-of-bounds Read in jfs_readdir run #16: crashed: KASAN: use-after-free Read in jfs_readdir run #17: crashed: KASAN: slab-out-of-bounds Read in jfs_readdir run #18: crashed: KASAN: slab-out-of-bounds Read in jfs_readdir run #19: crashed: KASAN: slab-out-of-bounds Read in jfs_readdir testing current HEAD a92b7d26c743b9dc06d520f863d624e94978a1d9 testing commit a92b7d26c743b9dc06d520f863d624e94978a1d9 gcc compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: e323269d7eaa1a1dc468519160c490930e46845102716c7599403d046355f5af run #0: crashed: KASAN: use-after-free Read in jfs_readdir run #1: crashed: KASAN: slab-use-after-free Read in jfs_readdir run #2: crashed: KASAN: slab-out-of-bounds Read in jfs_readdir run #3: crashed: KASAN: slab-out-of-bounds Read in jfs_readdir run #4: crashed: KASAN: use-after-free Read in jfs_readdir run #5: crashed: KASAN: slab-out-of-bounds Read in jfs_readdir run #6: crashed: KASAN: slab-out-of-bounds Read in jfs_readdir run #7: crashed: KASAN: slab-out-of-bounds Read in jfs_readdir run #8: crashed: KASAN: use-after-free Read in jfs_readdir run #9: crashed: KASAN: slab-out-of-bounds Read in jfs_readdir crash still not fixed/happens on the oldest tested release revisions tested: 2, total time: 54m17.94586961s (build: 45m0.091773043s, test: 7m30.723528246s) crash still not fixed on HEAD or HEAD had kernel test errors commit msg: Merge tag 'drm-fixes-2023-06-23' of git://anongit.freedesktop.org/drm/drm crash: KASAN: slab-out-of-bounds Read in jfs_readdir loop0: detected capacity change from 0 to 32768 ================================================================== BUG: KASAN: slab-out-of-bounds in jfs_readdir+0x2a98/0x3610 fs/jfs/jfs_dtree.c:2889 Read of size 1 at addr ffff88806fdf7f75 by task syz-executor.0/5714 CPU: 1 PID: 5714 Comm: syz-executor.0 Not tainted 6.4.0-rc7-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x64/0xb0 lib/dump_stack.c:106 print_address_description.constprop.0+0x2c/0x3c0 mm/kasan/report.c:351 print_report mm/kasan/report.c:462 [inline] kasan_report+0x11c/0x130 mm/kasan/report.c:572 jfs_readdir+0x2a98/0x3610 fs/jfs/jfs_dtree.c:2889 iterate_dir+0x1aa/0x6c0 fs/readdir.c:67 __do_sys_getdents64 fs/readdir.c:369 [inline] __se_sys_getdents64 fs/readdir.c:354 [inline] __x64_sys_getdents64+0x128/0x240 fs/readdir.c:354 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f57cce8c0f9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 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 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f57cdbe3168 EFLAGS: 00000246 ORIG_RAX: 00000000000000d9 RAX: ffffffffffffffda RBX: 00007f57ccfabf80 RCX: 00007f57cce8c0f9 RDX: 00000000000000c5 RSI: 0000000020000200 RDI: 0000000000000004 RBP: 00007f57ccee7b39 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fffa8bf8edf R14: 00007f57cdbe3300 R15: 0000000000022000 The buggy address belongs to the object at ffff88806fdf6e00 which belongs to the cache ext4_inode_cache of size 2432 The buggy address is located 2037 bytes to the right of allocated 2432-byte region [ffff88806fdf6e00, ffff88806fdf7780) The buggy address belongs to the physical page: page:ffffea0001bf7c00 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x6fdf0 head:ffffea0001bf7c00 order:3 entire_mapcount:0 nr_pages_mapped:0 pincount:0 memcg:ffff88807a82cb01 flags: 0xfff00000010200(slab|head|node=0|zone=1|lastcpupid=0x7ff) page_type: 0xffffffff() raw: 00fff00000010200 ffff888017db0500 dead000000000122 0000000000000000 raw: 0000000000000000 00000000800c000c 00000001ffffffff ffff88807a82cb01 page dumped because: kasan: bad access detected page_owner tracks the page as allocated page last allocated via order 3, migratetype Reclaimable, gfp_mask 0x1d2050(__GFP_IO|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_NOMEMALLOC|__GFP_HARDWALL|__GFP_RECLAIMABLE), pid 5711, tgid 5711 (syz-executor.0), ts 59289044350, free_ts 32404604199 prep_new_page mm/page_alloc.c:1738 [inline] get_page_from_freelist+0xf41/0x2c00 mm/page_alloc.c:3502 __alloc_pages+0x1cb/0x4a0 mm/page_alloc.c:4768 alloc_slab_page mm/slub.c:1851 [inline] allocate_slab+0x25f/0x390 mm/slub.c:1998 new_slab mm/slub.c:2051 [inline] ___slab_alloc+0xa91/0x1400 mm/slub.c:3192 __slab_alloc.constprop.0+0x56/0xa0 mm/slub.c:3291 __slab_alloc_node mm/slub.c:3344 [inline] slab_alloc_node mm/slub.c:3441 [inline] slab_alloc mm/slub.c:3459 [inline] __kmem_cache_alloc_lru mm/slub.c:3466 [inline] kmem_cache_alloc_lru+0x4a8/0x600 mm/slub.c:3482 alloc_inode_sb include/linux/fs.h:2705 [inline] ext4_alloc_inode+0x20/0x640 fs/ext4/super.c:1377 alloc_inode+0x56/0x1e0 fs/inode.c:260 new_inode_pseudo fs/inode.c:1018 [inline] new_inode+0x1a/0x240 fs/inode.c:1046 __ext4_new_inode+0x2e4/0x44f0 fs/ext4/ialloc.c:958 ext4_symlink+0x4c7/0x870 fs/ext4/namei.c:3393 vfs_symlink fs/namei.c:4475 [inline] vfs_symlink+0x3ee/0x630 fs/namei.c:4459 do_symlinkat+0x1ea/0x250 fs/namei.c:4501 __do_sys_symlinkat fs/namei.c:4517 [inline] __se_sys_symlinkat fs/namei.c:4514 [inline] __x64_sys_symlinkat+0x92/0xb0 fs/namei.c:4514 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd page last free stack trace: reset_page_owner include/linux/page_owner.h:24 [inline] free_pages_prepare mm/page_alloc.c:1302 [inline] free_unref_page_prepare+0x629/0xca0 mm/page_alloc.c:2564 free_unref_page+0x33/0x370 mm/page_alloc.c:2659 __folio_put_large mm/swap.c:119 [inline] release_pages+0x2ed/0x10e0 mm/swap.c:1008 tlb_batch_pages_flush+0x85/0x160 mm/mmu_gather.c:97 tlb_flush_mmu_free mm/mmu_gather.c:292 [inline] tlb_flush_mmu mm/mmu_gather.c:299 [inline] tlb_finish_mmu+0x114/0x6c0 mm/mmu_gather.c:391 exit_mmap+0x23d/0x750 mm/mmap.c:3120 __mmput+0xf3/0x440 kernel/fork.c:1351 exit_mm kernel/exit.c:567 [inline] do_exit+0x85d/0x24d0 kernel/exit.c:861 do_group_exit+0xb4/0x250 kernel/exit.c:1024 __do_sys_exit_group kernel/exit.c:1035 [inline] __se_sys_exit_group kernel/exit.c:1033 [inline] __x64_sys_exit_group+0x39/0x40 kernel/exit.c:1033 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd Memory state around the buggy address: ffff88806fdf7e00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ffff88806fdf7e80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc >ffff88806fdf7f00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ^ ffff88806fdf7f80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ffff88806fdf8000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ==================================================================