BUG: unable to handle kernel paging request in lookup_open

9 views
Skip to first unread message

syzbot

unread,
Dec 15, 2022, 4:59:35 AM12/15/22
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=155e9bc7880000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=4acbb046a8632405ae80
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/98c0bdb4abb3/disk-3f8a27f9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ea228ff02669/vmlinux-3f8a27f9.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+4acbb0...@syzkaller.appspotmail.com

ntfs: (device loop5): check_windows_hibernation_status(): Failed to find inode number for hiberfil.sys.
ntfs: volume version 3.1.
ntfs: (device loop5): load_system_files(): Failed to determine if Windows is hibernated. Mounting read-only. Run chkdsk.
ntfs: (device loop5): ntfs_lookup(): ntfs_lookup_ino_by_name() failed with error code 16777149.
BUG: unable to handle kernel paging request at ffffffffff00009b
PGD 9e6e067 P4D 9e6e067 PUD 9e70067 PMD 0
Oops: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 9866 Comm: syz-executor.5 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
RIP: 0010:lookup_open+0x70a/0x1a20 fs/namei.c:3228
Code: 85 ed 0f 85 39 0f 00 00 e8 03 d1 bc ff 48 8b 54 24 20 48 b8 00 00 00 00 00 fc ff df 48 c1 ea 03 80 3c 02 00 0f 85 b4 10 00 00 <48> 83 7d 58 00 0f 85 1c fc ff ff e8 d6 d0 bc ff 44 8b 6c 24 18 31
RSP: 0018:ffff88801410f9b8 EFLAGS: 00010246
RAX: dffffc0000000000 RBX: ffff88801410fce0 RCX: ffffc9000c279000
RDX: 1fffffffffe00013 RSI: ffffffff81a5b46d RDI: 0000000000000286
RBP: ffffffffff000043 R08: 0000000000000000 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000000 R12: 00000000ffffffe2
R13: ffffffffff000043 R14: ffff888090b04ec0 R15: ffff88801410fe90
FS: 00007f0bc0a0e700(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffff00009b CR3: 0000000040ff6000 CR4: 00000000003406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
do_last fs/namei.c:3327 [inline]
path_openat+0x1094/0x2df0 fs/namei.c:3537
ubi0: detaching mtd0
do_filp_open+0x18c/0x3f0 fs/namei.c:3567
ubi0: mtd0 is detached
do_sys_open+0x3b3/0x520 fs/open.c:1085
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f0bc249c0d9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f0bc0a0e168 EFLAGS: 00000246 ORIG_RAX: 0000000000000055
RAX: ffffffffffffffda RBX: 00007f0bc25bbf80 RCX: 00007f0bc249c0d9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000020000080
RBP: 00007f0bc24f7ae9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffd7155c21f R14: 00007f0bc0a0e300 R15: 0000000000022000
Modules linked in:
CR2: ffffffffff00009b
---[ end trace 2f568f04d4ddce1d ]---
RIP: 0010:lookup_open+0x70a/0x1a20 fs/namei.c:3228
Code: 85 ed 0f 85 39 0f 00 00 e8 03 d1 bc ff 48 8b 54 24 20 48 b8 00 00 00 00 00 fc ff df 48 c1 ea 03 80 3c 02 00 0f 85 b4 10 00 00 <48> 83 7d 58 00 0f 85 1c fc ff ff e8 d6 d0 bc ff 44 8b 6c 24 18 31
RSP: 0018:ffff88801410f9b8 EFLAGS: 00010246
RAX: dffffc0000000000 RBX: ffff88801410fce0 RCX: ffffc9000c279000
RDX: 1fffffffffe00013 RSI: ffffffff81a5b46d RDI: 0000000000000286
RBP: ffffffffff000043 R08: 0000000000000000 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000000 R12: 00000000ffffffe2
R13: ffffffffff000043 R14: ffff888090b04ec0 R15: ffff88801410fe90
FS: 00007f0bc0a0e700(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffff00009b CR3: 0000000040ff6000 CR4: 00000000003406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 85 ed test %ebp,%ebp
2: 0f 85 39 0f 00 00 jne 0xf41
8: e8 03 d1 bc ff callq 0xffbcd110
d: 48 8b 54 24 20 mov 0x20(%rsp),%rdx
12: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
19: fc ff df
1c: 48 c1 ea 03 shr $0x3,%rdx
20: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1)
24: 0f 85 b4 10 00 00 jne 0x10de
* 2a: 48 83 7d 58 00 cmpq $0x0,0x58(%rbp) <-- trapping instruction
2f: 0f 85 1c fc ff ff jne 0xfffffc51
35: e8 d6 d0 bc ff callq 0xffbcd110
3a: 44 8b 6c 24 18 mov 0x18(%rsp),%r13d
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 syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

syzbot

unread,
Dec 20, 2022, 4:52:29 AM12/20/22
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14ae693f880000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=4acbb046a8632405ae80
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=174a3f93880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10225000480000
mounted in repro: https://storage.googleapis.com/syzbot-assets/43a3d2ccdc6e/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+4acbb0...@syzkaller.appspotmail.com

ntfs: volume version 3.1.
ntfs: (device loop0): ntfs_lookup_inode_by_name(): Index entry out of bounds in directory inode 0x5.
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. Mounting read-only. Run chkdsk.
ntfs: (device loop0): ntfs_lookup(): ntfs_lookup_ino_by_name() failed with error code 16777149.
BUG: unable to handle kernel paging request at ffffffffff00009b
PGD 9e6e067 P4D 9e6e067 PUD 9e70067 PMD 0
Oops: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 8103 Comm: syz-executor380 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
RIP: 0010:lookup_open+0x70a/0x1a20 fs/namei.c:3228
Code: 85 ed 0f 85 39 0f 00 00 e8 03 d1 bc ff 48 8b 54 24 20 48 b8 00 00 00 00 00 fc ff df 48 c1 ea 03 80 3c 02 00 0f 85 b4 10 00 00 <48> 83 7d 58 00 0f 85 1c fc ff ff e8 d6 d0 bc ff 44 8b 6c 24 18 31
RSP: 0018:ffff8880921679b8 EFLAGS: 00010246
RAX: dffffc0000000000 RBX: ffff888092167ce0 RCX: 1ffff11016266d9e
RDX: 1fffffffffe00013 RSI: ffffffff81a5b46d RDI: 0000000000000286
RBP: ffffffffff000043 R08: 0000000000000000 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000000 R12: 00000000ffffffe2
R13: ffffffffff000043 R14: ffff88808e626ce0 R15: ffff888092167e90
FS: 0000555555da4300(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffff00009b CR3: 00000000b47cd000 CR4: 00000000003406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
do_last fs/namei.c:3327 [inline]
path_openat+0x1094/0x2df0 fs/namei.c:3537
do_filp_open+0x18c/0x3f0 fs/namei.c:3567
do_sys_open+0x3b3/0x520 fs/open.c:1085
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f3df5b19759
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:00007fff4664ea58 EFLAGS: 00000246 ORIG_RAX: 0000000000000055
RAX: ffffffffffffffda RBX: 0031656c69662f2e RCX: 00007f3df5b19759
RDX: 00007f3df5ad7dd3 RSI: 0000000000000000 RDI: 0000000020000080
RBP: 00007f3df5ad8ff0 R08: 000000000001ee42 R09: 0000000000000000
R10: 00007fff4664e920 R11: 0000000000000246 R12: 00007f3df5ad9080
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Modules linked in:
CR2: ffffffffff00009b
---[ end trace c90404bdd335f8fb ]---
RIP: 0010:lookup_open+0x70a/0x1a20 fs/namei.c:3228
Code: 85 ed 0f 85 39 0f 00 00 e8 03 d1 bc ff 48 8b 54 24 20 48 b8 00 00 00 00 00 fc ff df 48 c1 ea 03 80 3c 02 00 0f 85 b4 10 00 00 <48> 83 7d 58 00 0f 85 1c fc ff ff e8 d6 d0 bc ff 44 8b 6c 24 18 31
RSP: 0018:ffff8880921679b8 EFLAGS: 00010246
RAX: dffffc0000000000 RBX: ffff888092167ce0 RCX: 1ffff11016266d9e
RDX: 1fffffffffe00013 RSI: ffffffff81a5b46d RDI: 0000000000000286
RBP: ffffffffff000043 R08: 0000000000000000 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000000 R12: 00000000ffffffe2
R13: ffffffffff000043 R14: ffff88808e626ce0 R15: ffff888092167e90
FS: 0000555555da4300(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffff00009b CR3: 00000000b47cd000 CR4: 00000000003406e0

syzbot

unread,
Dec 24, 2022, 4:43:40 AM12/24/22
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: c4215ee4771b Linux 4.14.302
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=142502df880000
kernel config: https://syzkaller.appspot.com/x/.config?x=4a9988fe055c9527
dashboard link: https://syzkaller.appspot.com/bug?extid=a1f935f55c2cf6e0a1c4
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=124f9550480000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13aa9def880000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c93ba055d204/disk-c4215ee4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bfbc929a33c1/vmlinux-c4215ee4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/444658051770/bzImage-c4215ee4.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/49a71afbd3e6/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+a1f935...@syzkaller.appspotmail.com

ntfs: volume version 3.1.
ntfs: (device loop0): ntfs_lookup_inode_by_name(): Index entry out of bounds in directory inode 0x5.
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. Mounting read-only. Run chkdsk.
ntfs: (device loop0): ntfs_lookup(): ntfs_lookup_ino_by_name() failed with error code 16777149.
BUG: unable to handle kernel paging request at ffffffffff00009b
IP: lookup_open+0x625/0x1750 fs/namei.c:3234
PGD 8e6b067 P4D 8e6b067 PUD 8e6d067 PMD 0
Oops: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 1 PID: 7983 Comm: syz-executor293 Not tainted 4.14.302-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
task: ffff8880959d6200 task.stack: ffff888093638000
RIP: 0010:lookup_open+0x625/0x1750 fs/namei.c:3234
RSP: 0018:ffff88809363fa38 EFLAGS: 00010246
RAX: dffffc0000000000 RBX: ffff88809363fcf8 RCX: 1ffff11012b3ad56
RDX: 1fffffffffe00013 RSI: 0000000000000002 RDI: 0000000000000282
RBP: ffffffffff000043 R08: ffffffff8b9cf650 R09: 0000000000000001
R10: 0000000000000000 R11: ffff8880959d6200 R12: 00000000ffffffe2
R13: ffffffffff000043 R14: ffff8880941c1d20 R15: ffff88809363fe88
FS: 00005555566cc300(0000) GS:ffff8880ba500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffff00009b CR3: 00000000a1d93000 CR4: 00000000003406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
do_last fs/namei.c:3334 [inline]
path_openat+0xe08/0x2970 fs/namei.c:3571
do_filp_open+0x179/0x3c0 fs/namei.c:3605
do_sys_open+0x296/0x410 fs/open.c:1081
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x5e/0xd3
RIP: 0033:0x7fb1bba07759
RSP: 002b:00007ffcc06064e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000055
RAX: ffffffffffffffda RBX: 0031656c69662f2e RCX: 00007fb1bba07759
RDX: 00007fb1bb9c5dd3 RSI: 0000000000000000 RDI: 0000000020000080
RBP: 00007fb1bb9c6ff0 R08: 000000000001ee42 R09: 0000000000000000
R10: 00007ffcc06063b0 R11: 0000000000000246 R12: 00007fb1bb9c7080
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Code: 4d 85 ed 0f 85 45 0d 00 00 e8 28 c0 cb ff 48 8b 54 24 40 48 b8 00 00 00 00 00 fc ff df 48 c1 ea 03 80 3c 02 00 0f 85 a6 0e 00 00 <48> 83 7d 58 00 0f 85 b5 fc ff ff e8 fb bf cb ff f6 44 24 1c 40
RIP: lookup_open+0x625/0x1750 fs/namei.c:3234 RSP: ffff88809363fa38
CR2: ffffffffff00009b
---[ end trace 3424647b4596ea4b ]---
----------------
Code disassembly (best guess):
0: 4d 85 ed test %r13,%r13
3: 0f 85 45 0d 00 00 jne 0xd4e
9: e8 28 c0 cb ff callq 0xffcbc036
e: 48 8b 54 24 40 mov 0x40(%rsp),%rdx
13: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
1a: fc ff df
1d: 48 c1 ea 03 shr $0x3,%rdx
21: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1)
25: 0f 85 a6 0e 00 00 jne 0xed1
* 2b: 48 83 7d 58 00 cmpq $0x0,0x58(%rbp) <-- trapping instruction
30: 0f 85 b5 fc ff ff jne 0xfffffceb
36: e8 fb bf cb ff callq 0xffcbc036
3b: f6 44 24 1c 40 testb $0x40,0x1c(%rsp)


---
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 syzk...@googlegroups.com.

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
Reply all
Reply to author
Forward
0 new messages