ci2 starts bisection 2023-06-27 03:05:46.540009682 +0000 UTC m=+44365.630357539
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: feaf2d6fa29a4ab2c9c3bbbf5b0edb8e6089045e3ee324569de682587b574d54
all runs: crashed: KASAN: use-after-free Read in ntfs_read_folio
testing current HEAD 8d7868c41df58edabc4e408d119a1aef58a54d9d
testing commit 8d7868c41df58edabc4e408d119a1aef58a54d9d gcc
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
kernel signature: 5eebab12b4a530192a9a80a0be59683fb42db7ca9f7854e12bd37e3141d78f9a
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: out-of-bounds Read in ntfs_read_folio
run #9: crashed: KASAN: use-after-free Read in ntfs_read_folio
crash still not fixed/happens on the oldest tested release
revisions tested: 2, total time: 54m30.745741707s (build: 46m33.97876215s, test: 6m43.889397874s)
crash still not fixed on HEAD or HEAD had kernel test errors
commit msg: Merge tag 'thermal-6.5-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm
crash: KASAN: use-after-free Read in ntfs_read_folio
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 ffff88807205717f by task syz-executor.0/5425

CPU: 1 PID: 5425 Comm: syz-executor.0 Not tainted 6.4.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/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:351 [inline]
 print_report+0x163/0x540 mm/kasan/report.c:462
 kasan_report+0x176/0x1b0 mm/kasan/report.c:572
 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:2427
 do_read_cache_folio+0x104/0x590 mm/filemap.c:3703
 do_read_cache_page+0xf/0x160 mm/filemap.c:3769
 read_mapping_page include/linux/pagemap.h:772 [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+0x14e9/0x28c0 fs/ntfs/super.c:2900
 mount_bdev+0x232/0x340 fs/super.c:1392
 legacy_get_tree+0xe9/0x170 fs/fs_context.c:611
 vfs_get_tree+0x7f/0x220 fs/super.c:1520
 do_new_mount+0x1e5/0x940 fs/namespace.c:3335
 do_mount fs/namespace.c:3675 [inline]
 __do_sys_mount fs/namespace.c:3884 [inline]
 __se_sys_mount+0x232/0x2c0 fs/namespace.c:3861
 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:0x7fa2a068d62a
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:00007fa2a1494f88 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 000000000000097e RCX: 00007fa2a068d62a
RDX: 0000000020000040 RSI: 000000002001f200 RDI: 00007fa2a1494fe0
RBP: 00007fa2a1495020 R08: 00007fa2a1495020 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000020000040
R13: 000000002001f200 R14: 00007fa2a1494fe0 R15: 0000000020000000
 </TASK>

The buggy address belongs to the physical page:
page:ffffea0001c815c0 refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x72057
memcg:ffff88801537c000
flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff)
page_type: 0x0()
raw: 00fff000000a0014 ffffea0001f22188 ffffea0001c82008 ffff888029d46111
raw: 000000000000002e 0000000000000000 00000001ffffffff ffff88801537c000
page dumped because: kasan: bad access detected
page_owner tracks the page as freed
page last allocated via order 0, migratetype Movable, gfp_mask 0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), pid 5454, tgid 5454 (sed), ts 77333058817, free_ts 77354175102
 prep_new_page mm/page_alloc.c:1751 [inline]
 get_page_from_freelist+0x320e/0x3390 mm/page_alloc.c:3523
 __alloc_pages+0x255/0x670 mm/page_alloc.c:4794
 __folio_alloc+0x13/0x30 mm/page_alloc.c:4826
 vma_alloc_folio+0x308/0x680 mm/mempolicy.c:2240
 wp_page_copy mm/memory.c:3074 [inline]
 do_wp_page+0x8d1/0x2600 mm/memory.c:3432
 handle_pte_fault mm/memory.c:4964 [inline]
 __handle_mm_fault mm/memory.c:5089 [inline]
 handle_mm_fault+0x1e84/0x41f0 mm/memory.c:5243
 do_user_addr_fault arch/x86/mm/fault.c:1440 [inline]
 handle_page_fault arch/x86/mm/fault.c:1534 [inline]
 exc_page_fault+0x7c2/0x900 arch/x86/mm/fault.c:1590
 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:1308 [inline]
 free_unref_page_prepare+0x8fe/0xa10 mm/page_alloc.c:2577
 free_unref_page_list+0x596/0x830 mm/page_alloc.c:2718
 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+0x351/0x890 mm/mmap.c:3120
 __mmput+0xcb/0x300 kernel/fork.c:1351
 exit_mm+0x1de/0x290 kernel/exit.c:567
 do_exit+0x4f2/0x1d10 kernel/exit.c:861
 do_group_exit+0x1b9/0x280 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+0x3f/0x40 kernel/exit.c:1033
 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:
 ffff888072057000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff888072057080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff888072057100: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
                                                                ^
 ffff888072057180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff888072057200: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================