bisecting fixing commit since 13d2ce42de8cb98ff952f8de6307f896203854c2
building syzkaller on 821e0b09046a2f972ace26fbdc02aef1116792d4
testing commit 13d2ce42de8cb98ff952f8de6307f896203854c2 with gcc (GCC) 8.4.1 20210217
kernel signature: 9cddea049ae7f0d68bc5ddaaffa6a5c34ac4e32134439c60fa41c0463ce656db
run #0: crashed: KASAN: use-after-free Read in ntfs_iget
run #1: crashed: KASAN: use-after-free Read in ntfs_iget
run #2: crashed: KASAN: use-after-free Read in ntfs_iget
run #3: crashed: KASAN: use-after-free Read in ntfs_iget
run #4: crashed: KASAN: use-after-free Read in ntfs_iget
run #5: crashed: KASAN: use-after-free Read in ntfs_iget
run #6: crashed: KASAN: use-after-free Read in ntfs_iget
run #7: crashed: KASAN: use-after-free Read in ntfs_iget
run #8: crashed: KASAN: use-after-free Read in ntfs_iget
run #9: crashed: KASAN: use-after-free Read in ntfs_iget
run #10: crashed: KASAN: use-after-free Read in ntfs_iget
run #11: crashed: KASAN: use-after-free Read in ntfs_iget
run #12: crashed: KASAN: use-after-free Read in ntfs_iget
run #13: crashed: KASAN: use-after-free Read in ntfs_iget
run #14: crashed: KASAN: out-of-bounds Read in ntfs_iget
run #15: crashed: KASAN: use-after-free Read in ntfs_iget
run #16: crashed: KASAN: use-after-free Read in ntfs_iget
run #17: crashed: KASAN: use-after-free Read in ntfs_iget
run #18: crashed: KASAN: use-after-free Read in ntfs_iget
run #19: crashed: KASAN: use-after-free Read in ntfs_iget
testing current HEAD 2d19be4653f5e74ed95560b69f94eb6791d49af3
testing commit 2d19be4653f5e74ed95560b69f94eb6791d49af3 with gcc (GCC) 8.4.1 20210217
kernel signature: 27c1e2451d0ac352567df88937555fa52a535dfe6ce438fd4c274958ba1a7930
all runs: crashed: KASAN: use-after-free Read in ntfs_iget
revisions tested: 2, total time: 23m10.653230034s (build: 15m36.316137122s, test: 6m37.979464027s)
the crash still happens on HEAD
commit msg: Linux 4.19.177
crash: KASAN: use-after-free Read in ntfs_iget
IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
ntfs: (device loop2): is_boot_sector_ntfs(): Invalid end of sector marker.
ntfs: (device loop2): ntfs_is_extended_system_file(): Inode hard link count doesn't match number of name attributes. You should run chkdsk.
==================================================================
ntfs: (device loop2): ntfs_read_locked_inode(): $DATA attribute is missing.
BUG: KASAN: use-after-free in ntfs_read_locked_inode+0x413c/0x5200 fs/ntfs/inode.c:670
Read of size 8 at addr ffff88808106a3d5 by task syz-executor.1/9866

CPU: 1 PID: 9866 Comm: syz-executor.1 Not tainted 4.19.177-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0x17c/0x226 lib/dump_stack.c:118
 print_address_description.cold.6+0x9/0x211 mm/kasan/report.c:256
 kasan_report_error mm/kasan/report.c:354 [inline]
 kasan_report mm/kasan/report.c:412 [inline]
 kasan_report.cold.7+0x242/0x2fe mm/kasan/report.c:396
ntfs: (device loop2): ntfs_read_locked_inode(): Failed with error code -2.  Marking corrupt inode 0x1 as bad.  Run chkdsk.
 __asan_report_load_n_noabort+0xf/0x20 mm/kasan/report.c:443
 ntfs_read_locked_inode+0x413c/0x5200 fs/ntfs/inode.c:670
 ntfs_iget+0xe6/0x120 fs/ntfs/inode.c:190
 load_and_init_mft_mirror fs/ntfs/super.c:1041 [inline]
 load_system_files fs/ntfs/super.c:1786 [inline]
 ntfs_fill_super+0x13e3/0x79c0 fs/ntfs/super.c:2908
ntfs: (device loop2): load_system_files(): Failed to load $MFTMirr.  Mounting read-only.  Run ntfsfix and/or chkdsk.
 mount_bdev+0x26f/0x330 fs/super.c:1158
ntfs: (device loop2): map_mft_record_page(): Mft record 0xa is corrupt.  Run chkdsk.
 ntfs_mount+0x10/0x20 fs/ntfs/super.c:3065
 mount_fs+0x7f/0x2b0 fs/super.c:1261
 vfs_kern_mount.part.11+0x58/0x3d0 fs/namespace.c:961
 vfs_kern_mount fs/namespace.c:951 [inline]
 do_new_mount fs/namespace.c:2469 [inline]
 do_mount+0x376/0x2710 fs/namespace.c:2799
ntfs: (device loop2): map_mft_record(): Failed with error code 5.
 ksys_mount+0xb1/0xd0 fs/namespace.c:3015
 __do_sys_mount fs/namespace.c:3029 [inline]
 __se_sys_mount fs/namespace.c:3026 [inline]
 __x64_sys_mount+0xb9/0x150 fs/namespace.c:3026
 do_syscall_64+0xd0/0x4e0 arch/x86/entry/common.c:293
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
ntfs: (device loop2): ntfs_read_locked_inode(): Failed with error code -5.  Marking corrupt inode 0xa as bad.  Run chkdsk.
RIP: 0033:0x46701a
Code: 48 c7 c2 bc 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 bc ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fa2a661dfa8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000020000200 RCX: 000000000046701a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007fa2a661e000
RBP: 00007fa2a661e040 R08: 00007fa2a661e040 R09: 0000000020000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000020000000
R13: 0000000020000100 R14: 00007fa2a661e000 R15: 000000002007dc00

The buggy address belongs to the page:
page:ffffea0002041a80 count:0 mapcount:0 mapping:0000000000000000 index:0x1
flags: 0xfff00000000000()
raw: 00fff00000000000 ffffea0002041ac8 ffffea0002041a48 0000000000000000
raw: 0000000000000001 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
 ffff88808106a280: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff88808106a300: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>ffff88808106a380: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
                                                 ^
 ffff88808106a400: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff88808106a480: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================
ieee80211 phy10: Selected rate control algorithm 'minstrel_ht'
ntfs: (device loop2): load_and_init_upcase(): Failed to load $UpCase from the volume. Using default.