ci2 starts bisection 2023-12-04 15:59:25.133150489 +0000 UTC m=+400275.779727780 bisecting fixing commit since e6fda526d9db2c7897dacb9daff8c80e13ce893d building syzkaller on cdae481e33658b7c827516ae5c7f16007c505832 ensuring issue is reproducible on original commit e6fda526d9db2c7897dacb9daff8c80e13ce893d testing commit e6fda526d9db2c7897dacb9daff8c80e13ce893d gcc compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: a573e736d138b8454e5327f78a81941e20ced559e05b8ebbdc53ead8de99654a all runs: crashed: KASAN: out-of-bounds Read in ext4_ext_remove_space representative crash: KASAN: out-of-bounds Read in ext4_ext_remove_space, types: [KASAN] check whether we can drop unnecessary instrumentation disabling configs for [LEAK UBSAN BUG LOCKDEP ATOMIC_SLEEP HANG], they are not needed testing commit e6fda526d9db2c7897dacb9daff8c80e13ce893d gcc compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: 6f111984a7e9d72f39005c0e25501bf13de24cf98cc777d21c5dda2b65f462e0 all runs: crashed: KASAN: out-of-bounds Read in ext4_ext_remove_space representative crash: KASAN: out-of-bounds Read in ext4_ext_remove_space, types: [KASAN] the bug reproduces without the instrumentation disabling configs for [HANG LEAK UBSAN BUG LOCKDEP ATOMIC_SLEEP], they are not needed kconfig minimization: base=3915 full=7644 leaves diff=2002 split chunks (needed=false): <2002> split chunk #0 of len 2002 into 5 parts testing without sub-chunk 1/5 disabling configs for [HANG LEAK UBSAN BUG LOCKDEP ATOMIC_SLEEP], they are not needed testing commit e6fda526d9db2c7897dacb9daff8c80e13ce893d gcc compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: b6cfb56736b77f8aa1b2154461cbf8b012dda44a2fab01cb0db4e792cf4f06e4 all runs: crashed: KASAN: out-of-bounds Read in ext4_ext_remove_space representative crash: KASAN: out-of-bounds Read in ext4_ext_remove_space, types: [KASAN] the chunk can be dropped testing without sub-chunk 2/5 disabling configs for [UBSAN BUG LOCKDEP ATOMIC_SLEEP HANG LEAK], they are not needed testing commit e6fda526d9db2c7897dacb9daff8c80e13ce893d gcc compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: 66b35f31e4ce752dca3b568d201b25fe085a8e586beed4f3dd9e0667b6edc842 all runs: crashed: KASAN: out-of-bounds Read in ext4_ext_remove_space representative crash: KASAN: out-of-bounds Read in ext4_ext_remove_space, 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 e6fda526d9db2c7897dacb9daff8c80e13ce893d gcc compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: ea2a9b000852bdcd09799df40c990ba8aa63e27225265206ccbbac599fc22c2b all runs: crashed: KASAN: out-of-bounds Read in ext4_ext_remove_space representative crash: KASAN: out-of-bounds Read in ext4_ext_remove_space, 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 e6fda526d9db2c7897dacb9daff8c80e13ce893d gcc compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: f6d02d24cd53de82c11396abfc2ecdec7eb16f30dcbb793993413c0e0382fd64 run #0: crashed: KASAN: out-of-bounds Read in ext4_ext_remove_space run #1: crashed: KASAN: out-of-bounds Read in ext4_ext_remove_space run #2: crashed: KASAN: out-of-bounds Read in ext4_ext_remove_space run #3: crashed: KASAN: out-of-bounds Read in ext4_ext_remove_space run #4: crashed: KASAN: out-of-bounds Read in ext4_ext_remove_space run #5: crashed: KASAN: out-of-bounds Read in ext4_ext_remove_space run #6: crashed: KASAN: out-of-bounds Read in ext4_ext_remove_space run #7: crashed: KASAN: out-of-bounds Read in ext4_ext_remove_space run #8: crashed: KASAN: out-of-bounds Read in ext4_ext_remove_space run #9: OK representative crash: KASAN: out-of-bounds Read in ext4_ext_remove_space, types: [KASAN] the chunk can be dropped testing without sub-chunk 5/5 disabling configs for [LEAK UBSAN BUG LOCKDEP ATOMIC_SLEEP HANG], they are not needed testing commit e6fda526d9db2c7897dacb9daff8c80e13ce893d gcc compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: 18acec85a6a4e7c807b3e4961dd30b67859425cdc8787f083b806c82dba03076 all runs: crashed: KASAN: out-of-bounds Read in ext4_ext_remove_space representative crash: KASAN: out-of-bounds Read in ext4_ext_remove_space, types: [KASAN] the chunk can be dropped disabling configs for [HANG LEAK UBSAN BUG LOCKDEP ATOMIC_SLEEP], they are not needed testing current HEAD 33cc938e65a98f1d29d0a18403dbbee050dcad9a testing commit 33cc938e65a98f1d29d0a18403dbbee050dcad9a gcc compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 kernel signature: beb8b771af0416d4304318faa4e406f65451b3a3fe08f6a48bad442971c7abb0 run #0: crashed: KASAN: out-of-bounds Read in ext4_ext_remove_space run #1: crashed: KASAN: out-of-bounds Read in ext4_ext_remove_space run #2: crashed: KASAN: out-of-bounds Read in ext4_ext_remove_space run #3: crashed: KASAN: out-of-bounds Read in ext4_ext_remove_space run #4: crashed: KASAN: out-of-bounds Read in ext4_ext_remove_space run #5: crashed: KASAN: out-of-bounds Read in ext4_ext_remove_space run #6: crashed: KASAN: out-of-bounds Read in ext4_ext_remove_space run #7: crashed: KASAN: out-of-bounds Read in ext4_ext_remove_space run #8: OK run #9: OK representative crash: KASAN: out-of-bounds Read in ext4_ext_remove_space, types: [KASAN] crash still not fixed/happens on the oldest tested release revisions tested: 8, total time: 1h57m46.989551664s (build: 35m16.913620184s, test: 1h19m17.184179087s) crash still not fixed or there were kernel test errors commit msg: Linux 6.7-rc4 crash: KASAN: out-of-bounds Read in ext4_ext_remove_space EXT4-fs (loop0): Remounting filesystem read-only ================================================================== BUG: KASAN: out-of-bounds in ext4_ext_rm_leaf fs/ext4/extents.c:2736 [inline] BUG: KASAN: out-of-bounds in ext4_ext_remove_space+0x2076/0x4ac0 fs/ext4/extents.c:2958 Read of size 18446744073709551508 at addr ffff888129d12078 by task syz-executor.0/6593 CPU: 0 PID: 6593 Comm: syz-executor.0 Not tainted 6.7.0-rc4-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xf8/0x260 lib/dump_stack.c:106 print_address_description mm/kasan/report.c:364 [inline] print_report+0x163/0x540 mm/kasan/report.c:475 kasan_report+0x142/0x170 mm/kasan/report.c:588 kasan_check_range+0x27e/0x290 mm/kasan/generic.c:187 __asan_memmove+0x29/0x70 mm/kasan/shadow.c:94 ext4_ext_rm_leaf fs/ext4/extents.c:2736 [inline] ext4_ext_remove_space+0x2076/0x4ac0 fs/ext4/extents.c:2958 ext4_punch_hole+0x5b9/0x8c0 fs/ext4/inode.c:4019 ext4_fallocate+0x2c3/0x16e0 fs/ext4/extents.c:4707 vfs_fallocate+0x316/0x3d0 fs/open.c:324 do_vfs_ioctl+0x1b7e/0x2400 fs/ioctl.c:850 __do_sys_ioctl fs/ioctl.c:869 [inline] __se_sys_ioctl+0x4c/0xf0 fs/ioctl.c:857 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x45/0xe0 arch/x86/entry/common.c:82 entry_SYSCALL_64_after_hwframe+0x63/0x6b RIP: 0033:0x7f4722ddaae9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 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 b0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f471a57c0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f4722efa050 RCX: 00007f4722ddaae9 RDX: 0000000020000080 RSI: 000000004030582b RDI: 0000000000000004 RBP: 00007f4722e2647a R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 000000000000006e R14: 00007f4722efa050 R15: 00007ffc6022b508 The buggy address belongs to the physical page: page:ffffea0004a74480 refcount:2 mapcount:0 mapping:ffff888110510870 index:0x2b pfn:0x129d12 memcg:ffff88810935e000 aops:def_blk_aops ino:700000 flags: 0x20000000000812c(referenced|uptodate|lru|active|private|node=0|zone=2) page_type: 0xffffffff() raw: 020000000000812c ffffea0004a74648 ffff88810be4a030 ffff888110510870 raw: 000000000000002b ffff888125ee7e80 00000002ffffffff ffff88810935e000 page dumped because: kasan: bad access detected page_owner tracks the page as allocated page last allocated via order 0, migratetype Movable, gfp_mask 0x140c48(GFP_NOFS|__GFP_COMP|__GFP_HARDWALL|__GFP_MOVABLE), pid 6578, tgid 6576 (syz-executor.0), ts 108412380341, free_ts 108362946274 set_page_owner include/linux/page_owner.h:31 [inline] post_alloc_hook+0x10b/0x130 mm/page_alloc.c:1537 prep_new_page mm/page_alloc.c:1544 [inline] get_page_from_freelist+0x32d5/0x36a0 mm/page_alloc.c:3312 __alloc_pages+0x255/0x650 mm/page_alloc.c:4568 alloc_pages_mpol+0x143/0x320 mm/mempolicy.c:2133 alloc_pages mm/mempolicy.c:2204 [inline] folio_alloc+0xd4/0x1e0 mm/mempolicy.c:2211 filemap_alloc_folio+0xc6/0x3a0 mm/filemap.c:974 __filemap_get_folio+0x306/0x600 mm/filemap.c:1918 grow_dev_page fs/buffer.c:1041 [inline] grow_buffers fs/buffer.c:1106 [inline] __getblk_slow fs/buffer.c:1133 [inline] bdev_getblk+0x1b1/0x4c0 fs/buffer.c:1429 sb_getblk_gfp include/linux/buffer_head.h:370 [inline] ext4_ext_grow_indepth fs/ext4/extents.c:1334 [inline] ext4_ext_create_new_leaf fs/ext4/extents.c:1435 [inline] ext4_ext_insert_extent+0xf9b/0x55a0 fs/ext4/extents.c:2102 ext4_ext_map_blocks+0x1b81/0x6390 fs/ext4/extents.c:4306 ext4_map_blocks+0x831/0x1800 fs/ext4/inode.c:621 _ext4_get_block+0x1dc/0x5a0 fs/ext4/inode.c:763 __block_write_begin_int+0x3b7/0x1390 fs/buffer.c:2119 ext4_write_begin+0x5f8/0xfd0 ext4_da_write_begin+0x2b8/0x7b0 fs/ext4/inode.c:2875 generic_perform_write+0x30c/0x580 mm/filemap.c:3918 page last free stack trace: reset_page_owner include/linux/page_owner.h:24 [inline] free_pages_prepare mm/page_alloc.c:1137 [inline] free_unref_page_prepare+0x7e3/0x900 mm/page_alloc.c:2347 free_unref_page_list+0xb3/0x630 mm/page_alloc.c:2533 release_pages+0x174e/0x1900 mm/swap.c:1042 tlb_batch_pages_flush mm/mmu_gather.c:98 [inline] tlb_flush_mmu_free mm/mmu_gather.c:293 [inline] tlb_flush_mmu+0x273/0x3d0 mm/mmu_gather.c:300 zap_pte_range mm/memory.c:1543 [inline] zap_pmd_range mm/memory.c:1582 [inline] zap_pud_range mm/memory.c:1611 [inline] zap_p4d_range mm/memory.c:1632 [inline] unmap_page_range+0x17d3/0x1c00 mm/memory.c:1653 unmap_vmas+0x20b/0x2a0 mm/memory.c:1743 exit_mmap+0x244/0x960 mm/mmap.c:3308 __mmput+0x61/0x290 kernel/fork.c:1349 exit_mm+0x113/0x1b0 kernel/exit.c:567 do_exit+0x7ea/0x2440 kernel/exit.c:858 do_group_exit+0x1b9/0x280 kernel/exit.c:1021 get_signal+0x115a/0x12b0 kernel/signal.c:2904 arch_do_signal_or_restart+0x91/0x600 arch/x86/kernel/signal.c:309 exit_to_user_mode_loop+0x61/0xc0 kernel/entry/common.c:168 exit_to_user_mode_prepare+0x64/0xb0 kernel/entry/common.c:204 __syscall_exit_to_user_mode_work kernel/entry/common.c:285 [inline] syscall_exit_to_user_mode+0x2c/0x1e0 kernel/entry/common.c:296 Memory state around the buggy address: ffff888129d11f00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff888129d11f80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >ffff888129d12000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ^ ffff888129d12080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff888129d12100: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ==================================================================