ci2 starts bisection 2023-07-10 02:24:16.352601294 +0000 UTC m=+210049.933151693 bisecting fixing commit since d2869ace6eeb8ea8a6e70e6904524c5a6456d3fb building syzkaller on a4ae4f428721da42ac15f07d6f3b54584dedee27 ensuring issue is reproducible on original commit d2869ace6eeb8ea8a6e70e6904524c5a6456d3fb testing commit d2869ace6eeb8ea8a6e70e6904524c5a6456d3fb gcc compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: 391ccea4899299b18d93ef6a0b38cfd350df1b474e23045e8f421d75cf3b61c8 all runs: crashed: KASAN: slab-out-of-bounds Write in hfs_bnode_read_key representative crash: KASAN: slab-out-of-bounds Write in hfs_bnode_read_key, 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 d2869ace6eeb8ea8a6e70e6904524c5a6456d3fb gcc compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: 21c2cecfba7b01458f32c1aecb997d747bc36f166361b8c090abaf58e0ae9d16 all runs: crashed: KASAN: slab-out-of-bounds Write in hfs_bnode_read_key representative crash: KASAN: slab-out-of-bounds Write in hfs_bnode_read_key, types: [KASAN] the bug reproduces without the instrumentation disabling configs for [LEAK UBSAN BUG LOCKDEP ATOMIC_SLEEP HANG], they are not needed testing current HEAD 61fd484b2cf6bc8022e8e5ea6f693a9991740ac2 testing commit 61fd484b2cf6bc8022e8e5ea6f693a9991740ac2 gcc compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: 446e295f8e36e58e0869bcbf2bd59bb7631d68b81c989a83df8e44e2d39e9ad6 all runs: crashed: KASAN: slab-out-of-bounds Write in hfs_bnode_read_key representative crash: KASAN: slab-out-of-bounds Write in hfs_bnode_read_key, types: [KASAN] crash still not fixed/happens on the oldest tested release revisions tested: 3, total time: 3h4m13.551828717s (build: 2h30m37.786215143s, test: 9m12.550761668s) crash still not fixed on HEAD or HEAD had kernel test errors commit msg: Linux 6.1.38 crash: KASAN: slab-out-of-bounds Write in hfs_bnode_read_key loop0: detected capacity change from 0 to 64 hfs: unable to locate alternate MDB hfs: continuing without an alternate MDB ================================================================== BUG: KASAN: slab-out-of-bounds in memcpy_from_page include/linux/highmem.h:393 [inline] BUG: KASAN: slab-out-of-bounds in hfs_bnode_read fs/hfs/bnode.c:35 [inline] BUG: KASAN: slab-out-of-bounds in hfs_bnode_read_key+0x2b8/0x3b0 fs/hfs/bnode.c:70 Write of size 256 at addr ffff0000cf972800 by task syz-executor.0/4674 CPU: 1 PID: 4674 Comm: syz-executor.0 Not tainted 6.1.38-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023 Call trace: dump_backtrace+0x100/0x150 arch/arm64/kernel/stacktrace.c:158 show_stack+0x18/0x24 arch/arm64/kernel/stacktrace.c:165 __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x90/0xc8 lib/dump_stack.c:106 print_address_description mm/kasan/report.c:284 [inline] print_report+0x174/0x4c0 mm/kasan/report.c:395 kasan_report+0xd4/0x130 mm/kasan/report.c:495 kasan_check_range+0x264/0x2a4 mm/kasan/generic.c:189 memcpy+0x60/0x90 mm/kasan/shadow.c:66 memcpy_from_page include/linux/highmem.h:393 [inline] hfs_bnode_read fs/hfs/bnode.c:35 [inline] hfs_bnode_read_key+0x2b8/0x3b0 fs/hfs/bnode.c:70 hfs_brec_insert+0x498/0x8c8 fs/hfs/brec.c:141 hfs_cat_create+0x45c/0x778 fs/hfs/catalog.c:131 hfs_create+0x68/0xc4 fs/hfs/dir.c:202 lookup_open fs/namei.c:3413 [inline] open_last_lookups fs/namei.c:3481 [inline] path_openat+0xc04/0x1e98 fs/namei.c:3711 do_filp_open+0x1b0/0x394 fs/namei.c:3741 do_sys_openat2+0xfc/0x33c fs/open.c:1318 do_sys_open fs/open.c:1334 [inline] __do_sys_openat fs/open.c:1350 [inline] __se_sys_openat fs/open.c:1345 [inline] __arm64_sys_openat+0x1b0/0x200 fs/open.c:1345 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x7c/0x258 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x160/0x1e4 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x54/0x178 arch/arm64/kernel/syscall.c:206 el0_svc+0x58/0x13c arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581 Allocated by task 4674: kasan_save_stack mm/kasan/common.c:45 [inline] kasan_set_track+0x4c/0x80 mm/kasan/common.c:52 kasan_save_alloc_info+0x24/0x30 mm/kasan/generic.c:505 ____kasan_kmalloc mm/kasan/common.c:374 [inline] __kasan_kmalloc+0xac/0xc4 mm/kasan/common.c:383 kasan_kmalloc include/linux/kasan.h:211 [inline] __do_kmalloc_node mm/slab_common.c:955 [inline] __kmalloc+0xd0/0x23c mm/slab_common.c:968 kmalloc include/linux/slab.h:558 [inline] hfs_find_init+0x88/0x1a4 fs/hfs/bfind.c:21 hfs_cat_create+0x158/0x778 fs/hfs/catalog.c:96 hfs_create+0x68/0xc4 fs/hfs/dir.c:202 lookup_open fs/namei.c:3413 [inline] open_last_lookups fs/namei.c:3481 [inline] path_openat+0xc04/0x1e98 fs/namei.c:3711 do_filp_open+0x1b0/0x394 fs/namei.c:3741 do_sys_openat2+0xfc/0x33c fs/open.c:1318 do_sys_open fs/open.c:1334 [inline] __do_sys_openat fs/open.c:1350 [inline] __se_sys_openat fs/open.c:1345 [inline] __arm64_sys_openat+0x1b0/0x200 fs/open.c:1345 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x7c/0x258 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x160/0x1e4 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x54/0x178 arch/arm64/kernel/syscall.c:206 el0_svc+0x58/0x13c arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581 The buggy address belongs to the object at ffff0000cf972800 which belongs to the cache kmalloc-128 of size 128 The buggy address is located 0 bytes inside of 128-byte region [ffff0000cf972800, ffff0000cf972880) The buggy address belongs to the physical page: page:00000000b8709409 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x10f972 flags: 0x5ffc00000000200(slab|node=0|zone=2|lastcpupid=0x7ff) raw: 05ffc00000000200 fffffc00032f5380 dead000000000002 ffff0000c0002300 raw: 0000000000000000 0000000080100010 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff0000cf972700: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff0000cf972780: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc >ffff0000cf972800: 00 00 00 00 00 00 00 00 00 06 fc fc fc fc fc fc ^ ffff0000cf972880: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ffff0000cf972900: 00 00 00 00 fc fc fc fc fc fc fc fc fc fc fc fc ==================================================================