ci2 starts bisection 2023-04-16 20:12:44.099060485 +0000 UTC m=+199872.323961419
bisecting fixing commit since 38e04b3e4240a6d8fb43129ebad41608db64bc6f
building syzkaller on 7939252e4ddf50bbb9912069a40d32f6c83c4f8e
ensuring issue is reproducible on original commit 38e04b3e4240a6d8fb43129ebad41608db64bc6f

testing commit 38e04b3e4240a6d8fb43129ebad41608db64bc6f gcc
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
kernel signature: b9f2470b87c5385fa9c34a880e8409b88ff85dc4b08a046df27c962b0774c954
run #0: crashed: KASAN: use-after-free Read in ntfs_read_folio
run #1: crashed: KASAN: use-after-free Read in ntfs_read_folio
run #2: crashed: KASAN: use-after-free Read in ntfs_read_folio
run #3: crashed: KASAN: use-after-free Read in ntfs_read_folio
run #4: crashed: KASAN: use-after-free Read in ntfs_read_folio
run #5: crashed: KASAN: use-after-free Read in ntfs_read_folio
run #6: crashed: KASAN: use-after-free Read in ntfs_read_folio
run #7: crashed: KASAN: use-after-free Read in ntfs_read_folio
run #8: crashed: KASAN: use-after-free Read in ntfs_read_folio
run #9: crashed: KASAN: use-after-free Read in ntfs_read_folio
run #10: crashed: KASAN: use-after-free Read in ntfs_read_folio
run #11: crashed: KASAN: use-after-free Read in ntfs_read_folio
run #12: crashed: KASAN: use-after-free Read in ntfs_read_folio
run #13: crashed: KASAN: use-after-free Read in ntfs_read_folio
run #14: crashed: KASAN: use-after-free Read in ntfs_read_folio
run #15: crashed: KASAN: use-after-free Read in ntfs_read_folio
run #16: crashed: KASAN: out-of-bounds Read in ntfs_read_folio
run #17: crashed: KASAN: use-after-free Read in ntfs_read_folio
run #18: crashed: KASAN: use-after-free Read in ntfs_read_folio
run #19: crashed: KASAN: use-after-free Read in ntfs_read_folio
testing current HEAD 6c538e1adbfc696ac4747fb10d63e704344f763d
testing commit 6c538e1adbfc696ac4747fb10d63e704344f763d gcc
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
kernel signature: cedd4b810dbaddfb6d62782a561e48cbadbe340856a56c746e725953d91b7530
all runs: crashed: KASAN: use-after-free Read in ntfs_read_folio
revisions tested: 2, total time: 45m0.68273904s (build: 36m15.653935842s, test: 6m25.327319309s)
the crash still happens on HEAD
commit msg: Merge tag 'sched_urgent_for_v6.3_rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
crash: KASAN: use-after-free Read in ntfs_read_folio
ntfs: (device loop0): ntfs_external_attr_find(): Base inode 0xa contains corrupt attribute list attribute. Unmount and run chkdsk.
ntfs: (device loop0): ntfs_read_locked_inode(): Failed to lookup $DATA attribute.
ntfs: (device loop0): ntfs_read_locked_inode(): Failed with error code -5.  Marking corrupt inode 0xa as bad.  Run chkdsk.
ntfs: (device loop0): load_and_init_upcase(): Failed to load $UpCase from the volume. Using default.
==================================================================
BUG: KASAN: use-after-free in ntfs_read_folio+0x7d2/0x2040 fs/ntfs/aops.c:489
Read of size 1 at addr ffff88806e9ea17f by task syz-executor.0/5619

CPU: 0 PID: 5619 Comm: syz-executor.0 Not tainted 6.3.0-rc6-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/30/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x167/0x220 lib/dump_stack.c:106
 print_address_description mm/kasan/report.c:319 [inline]
 print_report+0x163/0x540 mm/kasan/report.c:430
 kasan_report+0x176/0x1b0 mm/kasan/report.c:536
 kasan_check_range+0x283/0x290 mm/kasan/generic.c:187
 __asan_memcpy+0x29/0x70 mm/kasan/shadow.c:105
 ntfs_read_folio+0x7d2/0x2040 fs/ntfs/aops.c:489
 filemap_read_folio+0x14e/0x530 mm/filemap.c:2424
 do_read_cache_folio+0x239/0x570 mm/filemap.c:3683
 do_read_cache_page+0xf/0x160 mm/filemap.c:3749
 read_mapping_page include/linux/pagemap.h:769 [inline]
 ntfs_map_page fs/ntfs/aops.h:75 [inline]
 load_and_init_attrdef fs/ntfs/super.c:1617 [inline]
 load_system_files+0x1df9/0x3ff0 fs/ntfs/super.c:1825
 ntfs_fill_super+0x14ea/0x28c0 fs/ntfs/super.c:2900
 mount_bdev+0x27f/0x370 fs/super.c:1380
 legacy_get_tree+0xe9/0x170 fs/fs_context.c:610
 vfs_get_tree+0x7f/0x220 fs/super.c:1510
 do_new_mount+0x1e5/0x940 fs/namespace.c:3042
 do_mount fs/namespace.c:3385 [inline]
 __do_sys_mount fs/namespace.c:3594 [inline]
 __se_sys_mount+0x232/0x2c0 fs/namespace.c:3571
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fcc6168d62a
Code: 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 b8 04 00 00 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 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:00007fcc6238df88 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 000000000000097e RCX: 00007fcc6168d62a
RDX: 0000000020000040 RSI: 000000002001f200 RDI: 00007fcc6238dfe0
RBP: 00007fcc6238e020 R08: 00007fcc6238e020 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000020000040
R13: 000000002001f200 R14: 00007fcc6238dfe0 R15: 0000000020000000
 </TASK>

The buggy address belongs to the physical page:
page:ffffea0001ba7a80 refcount:1 mapcount:1 mapping:0000000000000000 index:0x7f1c55a63 pfn:0x6e9ea
flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff)
raw: 00fff00000000000 ffffea0001ba79c8 ffffea0001ba1f08 0000000000000000
raw: 0000000000000001 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 0, migratetype Movable, gfp_mask 0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), pid 5643, tgid 5643 (cmp), ts 73360417218, free_ts 73376702096
 prep_new_page mm/page_alloc.c:2553 [inline]
 get_page_from_freelist+0x3246/0x33c0 mm/page_alloc.c:4326
 __alloc_pages+0x255/0x670 mm/page_alloc.c:5592
 __folio_alloc+0x13/0x30 mm/page_alloc.c:5624
 vma_alloc_folio+0x308/0x680 mm/mempolicy.c:2244
 wp_page_copy mm/memory.c:3068 [inline]
 do_wp_page+0x8d1/0x25f0 mm/memory.c:3426
 handle_pte_fault mm/memory.c:4941 [inline]
 __handle_mm_fault mm/memory.c:5065 [inline]
 handle_mm_fault+0x1fe0/0x3ce0 mm/memory.c:5211
 do_user_addr_fault arch/x86/mm/fault.c:1407 [inline]
 handle_page_fault arch/x86/mm/fault.c:1498 [inline]
 exc_page_fault+0x5b1/0x7c0 arch/x86/mm/fault.c:1554
 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570
page last free stack trace:
 reset_page_owner include/linux/page_owner.h:24 [inline]
 free_pages_prepare mm/page_alloc.c:1454 [inline]
 free_pcp_prepare mm/page_alloc.c:1504 [inline]
 free_unref_page_prepare+0xe2f/0xe70 mm/page_alloc.c:3388
 free_unref_page_list+0x596/0x830 mm/page_alloc.c:3529
 release_pages+0x1a0f/0x1bc0 mm/swap.c:1042
 tlb_batch_pages_flush mm/mmu_gather.c:97 [inline]
 tlb_flush_mmu_free mm/mmu_gather.c:292 [inline]
 tlb_flush_mmu+0xe9/0x1e0 mm/mmu_gather.c:299
 tlb_finish_mmu+0xb6/0x1c0 mm/mmu_gather.c:391
 exit_mmap+0x358/0x7d0 mm/mmap.c:3043
 __mmput+0xcb/0x300 kernel/fork.c:1207
 exit_mm+0x1de/0x290 kernel/exit.c:563
 do_exit+0x4f2/0x1d10 kernel/exit.c:856
 do_group_exit+0x1b9/0x280 kernel/exit.c:1019
 __do_sys_exit_group kernel/exit.c:1030 [inline]
 __se_sys_exit_group kernel/exit.c:1028 [inline]
 __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1028
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd

Memory state around the buggy address:
 ffff88806e9ea000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff88806e9ea080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>ffff88806e9ea100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
                                                                ^
 ffff88806e9ea180: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff88806e9ea200: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================