[syzbot] [ntfs?] BUG: unable to handle kernel paging request in step_into
From: syzbot
Date: Wed Jan 04 2023 - 03:33:07 EST
Hello,
syzbot found the following issue on:
HEAD commit: bff687b3dad6 Merge tag 'block-6.2-2022-12-29' of git://git..
git tree: upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=10341ca2480000
kernel config: https://syzkaller.appspot.com/x/.config?x=68e0be42c8ee4bb4
dashboard link: https://syzkaller.appspot.com/bug?extid=0994679b6f098bb3da6d
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11307974480000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15c567f2480000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b1982d688f97/disk-bff687b3.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c7c5609f900d/vmlinux-bff687b3.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ee4e79832281/bzImage-bff687b3.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/ad10dc248cd4/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+0994679b6f098bb3da6d@xxxxxxxxxxxxxxxxxxxxxxxxx
ntfs: (device loop0): check_windows_hibernation_status(): Failed to find inode number for hiberfil.sys.
ntfs: (device loop0): load_system_files(): Failed to determine if Windows is hibernated. Will not be able to remount read-write. Run chkdsk.
ntfs: (device loop0): ntfs_lookup(): ntfs_lookup_ino_by_name() failed with error code 83886016.
BUG: unable to handle page fault for address: fffffbffff600008
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD 23ffe4067 P4D 23ffe4067 PUD 23ffe3067 PMD 0
Oops: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 5067 Comm: syz-executor133 Not tainted 6.2.0-rc1-syzkaller-00068-gbff687b3dad6 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
RIP: 0010:traverse_mounts fs/namei.c:1428 [inline]
RIP: 0010:handle_mounts fs/namei.c:1540 [inline]
RIP: 0010:step_into+0x197/0x10f0 fs/namei.c:1831
Code: 38 00 49 89 c7 74 0a 48 8b 7c 24 38 e8 b2 60 ec ff 48 8b 9c 24 d8 00 00 00 48 89 d8 48 c1 e8 03 48 b9 00 00 00 00 00 fc ff df <8a> 04 08 84 c0 0f 85 4f 0c 00 00 8b 1b 89 de 81 e6 00 00 07 00 31
RSP: 0018:ffffc90003b8f680 EFLAGS: 00010a02
RAX: 1fffffffff600008 RBX: fffffffffb000040 RCX: dffffc0000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90003b8f7e0 R08: ffffffff81f52253 R09: ffffed100e6185a9
R10: ffffed100e6185a9 R11: 1ffff1100e6185a8 R12: ffffc90003b8f750
R13: ffffc90003b8fba0 R14: 0000000000000000 R15: 1ffff92000771eeb
FS: 0000555555c7b300(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffffbffff600008 CR3: 0000000071d1d000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
lookup_last fs/namei.c:2450 [inline]
path_lookupat+0x17d/0x450 fs/namei.c:2474
do_o_path+0x84/0x240 fs/namei.c:3685
path_openat+0x27cd/0x2dd0 fs/namei.c:3707
do_filp_open+0x264/0x4f0 fs/namei.c:3741
do_sys_openat2+0x124/0x4e0 fs/open.c:1310
do_sys_open fs/open.c:1326 [inline]
__do_sys_open fs/open.c:1334 [inline]
__se_sys_open fs/open.c:1330 [inline]
__x64_sys_open+0x221/0x270 fs/open.c:1330
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f51b212dc49
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 14 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 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffe3c84b5d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 0030656c69662f2e RCX: 00007f51b212dc49
RDX: 0000000000000000 RSI: 0000000001ee0000 RDI: 0000000020000340
RBP: 00007f51b20ed250 R08: 00007ffe3c84b4b0 R09: 0000000000000000
R10: 00007ffe3c84b4a0 R11: 0000000000000246 R12: 00007f51b20ed2e0
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
</TASK>
Modules linked in:
CR2: fffffbffff600008
---[ end trace 0000000000000000 ]---
RIP: 0010:traverse_mounts fs/namei.c:1428 [inline]
RIP: 0010:handle_mounts fs/namei.c:1540 [inline]
RIP: 0010:step_into+0x197/0x10f0 fs/namei.c:1831
Code: 38 00 49 89 c7 74 0a 48 8b 7c 24 38 e8 b2 60 ec ff 48 8b 9c 24 d8 00 00 00 48 89 d8 48 c1 e8 03 48 b9 00 00 00 00 00 fc ff df <8a> 04 08 84 c0 0f 85 4f 0c 00 00 8b 1b 89 de 81 e6 00 00 07 00 31
RSP: 0018:ffffc90003b8f680 EFLAGS: 00010a02
RAX: 1fffffffff600008 RBX: fffffffffb000040 RCX: dffffc0000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90003b8f7e0 R08: ffffffff81f52253 R09: ffffed100e6185a9
R10: ffffed100e6185a9 R11: 1ffff1100e6185a8 R12: ffffc90003b8f750
R13: ffffc90003b8fba0 R14: 0000000000000000 R15: 1ffff92000771eeb
FS: 0000555555c7b300(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffffbffff600008 CR3: 0000000071d1d000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 38 00 cmp %al,(%rax)
2: 49 89 c7 mov %rax,%r15
5: 74 0a je 0x11
7: 48 8b 7c 24 38 mov 0x38(%rsp),%rdi
c: e8 b2 60 ec ff callq 0xffec60c3
11: 48 8b 9c 24 d8 00 00 mov 0xd8(%rsp),%rbx
18: 00
19: 48 89 d8 mov %rbx,%rax
1c: 48 c1 e8 03 shr $0x3,%rax
20: 48 b9 00 00 00 00 00 movabs $0xdffffc0000000000,%rcx
27: fc ff df
* 2a: 8a 04 08 mov (%rax,%rcx,1),%al <-- trapping instruction
2d: 84 c0 test %al,%al
2f: 0f 85 4f 0c 00 00 jne 0xc84
35: 8b 1b mov (%rbx),%ebx
37: 89 de mov %ebx,%esi
39: 81 e6 00 00 07 00 and $0x70000,%esi
3f: 31 .byte 0x31
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@xxxxxxxxxxxxxxxx.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches