syzbot


BUG: unable to handle kernel paging request in path_openat

Status: auto-obsoleted due to no activity on 2024/04/12 10:28
Subsystems: reiserfs
[Documentation on labels]
Reported-by: syzbot+59a66cac604a6b49ecce@syzkaller.appspotmail.com
First crash: 718d, last: 310d
Cause bisection: failed (error log, bisect log)
  
Fix bisection: the issue occurs on the latest tested release (bisect log)
  
Discussions (2)
Title Replies (including bot) Last reply
[syzbot] Monthly reiserfs report 0 (1) 2023/03/27 11:03
[syzbot] BUG: unable to handle kernel paging request in path_openat 0 (2) 2022/12/15 12:09
Similar bugs (7)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-5-10 general protection fault in path_openat C done 30 6d08h 537d 0/2 upstream: reported C repro on 2023/05/21 01:33
android-5-15 general protection fault in path_openat origin:downstream C done 7 15d 537d 0/2 upstream: reported C repro on 2023/05/21 01:53
android-6-1 general protection fault in path_openat origin:downstream C done error 6 71d 537d 0/2 upstream: reported C repro on 2023/05/21 01:53
linux-4.19 general protection fault in path_openat C done 13 1738d 1744d 1/1 fixed on 2020/03/06 08:34
upstream general protection fault in path_openat ext4 C done 7 1742d 1742d 15/28 fixed on 2020/02/18 14:31
linux-4.14 general protection fault in path_openat C done 40 1738d 1745d 1/1 fixed on 2020/03/06 21:15
android-54 general protection fault in path_openat syz 26 1737d 1744d 1/2 fixed on 2021/10/12 13:38
Last patch testing requests (11)
Created Duration User Patch Repo Result
2024/03/13 11:25 17m retest repro upstream OK log
2024/02/06 15:43 19m retest repro upstream OK log
2024/01/18 08:20 21m retest repro linux-next OK log
2024/01/03 10:12 14m retest repro upstream report log
2023/11/28 15:20 11m retest repro upstream report log
2023/11/09 00:12 1m retest repro linux-next error
2023/11/08 20:15 22m retest repro upstream OK log
2023/10/25 06:40 3h15m retest repro linux-next OK log
2023/10/25 08:45 15m retest repro upstream report log
2023/10/25 08:45 21m retest repro upstream OK log
2022/12/15 12:59 23m hdanton@sina.com patch https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master OK log

Sample crash report:
REISERFS (device loop2): Created .reiserfs_priv - reserved for xattr storage.
BUG: unable to handle page fault for address: fffffffffff8231d
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD d08f067 P4D d08f067 PUD d091067 PMD 0 
Oops: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 5474 Comm: syz-executor332 Not tainted 6.2.0-rc4-syzkaller-00031-g6e50979a9c87 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023
RIP: 0010:__d_entry_type include/linux/dcache.h:385 [inline]
RIP: 0010:d_can_lookup include/linux/dcache.h:400 [inline]
RIP: 0010:d_is_dir include/linux/dcache.h:410 [inline]
RIP: 0010:do_open fs/namei.c:3533 [inline]
RIP: 0010:path_openat+0x210d/0x2dd0 fs/namei.c:3714
Code: 42 80 3c 20 00 74 08 4c 89 f7 e8 1e 62 ed ff 4d 8b 36 4c 89 f0 48 c1 e8 03 42 8a 04 20 84 c0 0f 85 bf 09 00 00 bb 00 00 60 00 <41> 23 1e bf 00 00 20 00 89 de e8 54 b6 97 ff 81 fb 00 00 20 00 75
RSP: 0018:ffffc9000934f920 EFLAGS: 00010246

RAX: 1fffffffffff0400 RBX: 0000000000600000 RCX: ffff888025093a80
RDX: 0000000000000000 RSI: 0000000000000042 RDI: 00000000000000ff
RBP: ffffc9000934fb50 R08: ffffffff81f42911 R09: fffffbfff1d2d28e
R10: fffffbfff1d2d28e R11: 1ffffffff1d2d28d R12: dffffc0000000000
R13: ffffc9000934fba0 R14: fffffffffff8231d R15: ffffc9000934fda0
FS:  00007fc500c54700(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffffffffff8231d CR3: 00000000225dc000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 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_openat fs/open.c:1342 [inline]
 __se_sys_openat fs/open.c:1337 [inline]
 __x64_sys_openat+0x243/0x290 fs/open.c:1337
 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:0x7fc500ca8ac9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 71 15 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:00007fc500c54208 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007fc500d2e7a8 RCX: 00007fc500ca8ac9
RDX: 0000000000141842 RSI: 0000000020000380 RDI: 00000000ffffff9c
RBP: 00007fc500d2e7a0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fc500d2e7ac
R13: 00007fffdeb1622f R14: 00007fc500c54300 R15: 0000000000022000
 </TASK>
Modules linked in:
CR2: fffffffffff8231d
---[ end trace 0000000000000000 ]---
RIP: 0010:__d_entry_type include/linux/dcache.h:385 [inline]
RIP: 0010:d_can_lookup include/linux/dcache.h:400 [inline]
RIP: 0010:d_is_dir include/linux/dcache.h:410 [inline]
RIP: 0010:do_open fs/namei.c:3533 [inline]
RIP: 0010:path_openat+0x210d/0x2dd0 fs/namei.c:3714
Code: 42 80 3c 20 00 74 08 4c 89 f7 e8 1e 62 ed ff 4d 8b 36 4c 89 f0 48 c1 e8 03 42 8a 04 20 84 c0 0f 85 bf 09 00 00 bb 00 00 60 00 <41> 23 1e bf 00 00 20 00 89 de e8 54 b6 97 ff 81 fb 00 00 20 00 75
RSP: 0018:ffffc9000934f920 EFLAGS: 00010246
RAX: 1fffffffffff0400 RBX: 0000000000600000 RCX: ffff888025093a80
RDX: 0000000000000000 RSI: 0000000000000042 RDI: 00000000000000ff
RBP: ffffc9000934fb50 R08: ffffffff81f42911 R09: fffffbfff1d2d28e
R10: fffffbfff1d2d28e R11: 1ffffffff1d2d28d R12: dffffc0000000000
R13: ffffc9000934fba0 R14: fffffffffff8231d R15: ffffc9000934fda0
FS:  00007fc500c54700(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffffffffff8231d CR3: 00000000225dc000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
   0:	42 80 3c 20 00       	cmpb   $0x0,(%rax,%r12,1)
   5:	74 08                	je     0xf
   7:	4c 89 f7             	mov    %r14,%rdi
   a:	e8 1e 62 ed ff       	callq  0xffed622d
   f:	4d 8b 36             	mov    (%r14),%r14
  12:	4c 89 f0             	mov    %r14,%rax
  15:	48 c1 e8 03          	shr    $0x3,%rax
  19:	42 8a 04 20          	mov    (%rax,%r12,1),%al
  1d:	84 c0                	test   %al,%al
  1f:	0f 85 bf 09 00 00    	jne    0x9e4
  25:	bb 00 00 60 00       	mov    $0x600000,%ebx
* 2a:	41 23 1e             	and    (%r14),%ebx <-- trapping instruction
  2d:	bf 00 00 20 00       	mov    $0x200000,%edi
  32:	89 de                	mov    %ebx,%esi
  34:	e8 54 b6 97 ff       	callq  0xff97b68d
  39:	81 fb 00 00 20 00    	cmp    $0x200000,%ebx
  3f:	75                   	.byte 0x75

Crashes (52):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/01/18 08:51 upstream 6e50979a9c87 42660d9e .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs BUG: unable to handle kernel paging request in path_openat
2022/12/19 07:33 upstream f9ff5644bcc0 05494336 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root BUG: unable to handle kernel paging request in path_openat
2022/12/15 12:09 upstream 041fae9c105a 6f9c033e .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs BUG: unable to handle kernel paging request in path_openat
2022/12/28 04:58 upstream 1b929c02afd3 44712fbc .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs general protection fault in path_openat
2023/02/28 22:14 linux-next 058f4df42121 95aee97a .config console log report syz [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root general protection fault in path_openat
2023/02/26 21:47 linux-next 8232539f864c ee50e71c .config console log report syz [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root general protection fault in path_openat
2023/06/07 06:12 upstream a4d7d7011219 a4ae4f42 .config console log report info ci-upstream-kasan-gce-selinux-root BUG: unable to handle kernel paging request in path_openat
2023/06/02 04:53 upstream 1874a42a7d74 a4ae4f42 .config console log report info ci-qemu-upstream BUG: unable to handle kernel paging request in path_openat
2023/05/14 15:57 upstream bb7c241fae62 2b9ba477 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root BUG: unable to handle kernel paging request in path_openat
2023/04/16 00:12 upstream 7a934f4bd7d6 ec410564 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root BUG: unable to handle kernel paging request in path_openat
2023/03/29 00:04 upstream 3a93e40326c8 48c74771 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root BUG: unable to handle kernel paging request in path_openat
2023/02/19 16:09 upstream 925cf0457d7e bcdf85f8 .config console log report info ci-upstream-kasan-gce-root BUG: unable to handle kernel paging request in path_openat
2023/02/03 10:33 upstream 66a87fff1a87 16d19e30 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root BUG: unable to handle kernel paging request in path_openat
2023/02/01 15:59 upstream c0b67534c95c 9a6f477c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs BUG: unable to handle kernel paging request in path_openat
2023/01/30 08:21 upstream ab072681eabe 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs BUG: unable to handle kernel paging request in path_openat
2023/01/26 08:36 upstream 7c46948a6e9c 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs BUG: unable to handle kernel paging request in path_openat
2023/01/23 18:37 upstream 2475bf0250de 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs BUG: unable to handle kernel paging request in path_openat
2023/01/18 01:39 upstream 6e50979a9c87 aedf5331 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root BUG: unable to handle kernel paging request in path_openat
2023/01/17 23:29 upstream 6e50979a9c87 42660d9e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs BUG: unable to handle kernel paging request in path_openat
2023/01/17 15:47 upstream d532dd102151 a63719e7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs BUG: unable to handle kernel paging request in path_openat
2023/01/15 07:11 upstream 7c6984405241 a63719e7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs BUG: unable to handle kernel paging request in path_openat
2023/01/07 15:35 upstream 0a71553536d2 1dac8c7a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs BUG: unable to handle kernel paging request in path_openat
2023/01/04 14:57 upstream 69b41ac87e4a 1dac8c7a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs BUG: unable to handle kernel paging request in path_openat
2023/01/04 14:15 upstream 69b41ac87e4a 1dac8c7a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs BUG: unable to handle kernel paging request in path_openat
2023/01/01 11:05 upstream c8451c141e07 ab32d508 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs BUG: unable to handle kernel paging request in path_openat
2022/12/31 11:39 upstream bff687b3dad6 ab32d508 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs BUG: unable to handle kernel paging request in path_openat
2022/12/25 08:09 upstream 72a85e2b0a1e 9da18ae8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs BUG: unable to handle kernel paging request in path_openat
2022/12/23 21:33 upstream 8395ae05cb5a 9da18ae8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs BUG: unable to handle kernel paging request in path_openat
2022/12/22 08:36 upstream 9d2f6060fe4c 4067838e .config console log report info ci-upstream-kasan-gce-root BUG: unable to handle kernel paging request in path_openat
2022/12/21 21:54 upstream b6bb9676f216 4067838e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs BUG: unable to handle kernel paging request in path_openat
2022/12/04 18:35 upstream c2bf05db6c78 e080de16 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs BUG: unable to handle kernel paging request in path_openat
2022/11/28 02:50 upstream cf562a45a0d5 f4470a7b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs BUG: unable to handle kernel paging request in path_openat
2022/11/26 22:25 upstream 644e9524388a f4470a7b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs BUG: unable to handle kernel paging request in path_openat
2022/11/21 07:34 upstream eb7081409f94 5bb70014 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs BUG: unable to handle kernel paging request in path_openat
2023/04/15 21:07 upstream 7a934f4bd7d6 ec410564 .config console log report info ci-qemu-upstream-386 BUG: unable to handle kernel paging request in path_openat
2023/02/23 22:14 upstream a5c95ca18a98 4359978e .config console log report info ci-qemu-upstream-386 BUG: unable to handle kernel paging request in path_openat
2023/01/10 01:13 linux-next 543b9b2fe10b 1dac8c7a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root BUG: unable to handle kernel paging request in path_openat
2023/03/19 17:29 upstream a3671bd86a97 7939252e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root general protection fault in path_openat
2023/03/05 13:39 upstream b01fe98d34f3 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root general protection fault in path_openat
2023/03/03 15:07 upstream 2eb29d59ddf0 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root general protection fault in path_openat
2023/01/31 02:00 upstream 6d796c50f84c b68fb8d6 .config console log report info ci2-upstream-fs general protection fault in path_openat
2023/01/27 12:43 upstream 7c46948a6e9c 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in path_openat
2023/01/19 14:43 upstream 7287904c8771 66fca3ae .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in path_openat
2023/01/13 21:08 upstream d9fc1511728c 529798b0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in path_openat
2023/01/05 05:15 upstream 512dee0c00ad 1dac8c7a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in path_openat
2022/12/25 21:10 upstream 72a85e2b0a1e 9da18ae8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in path_openat
2022/12/22 00:43 upstream b6bb9676f216 4067838e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in path_openat
2022/12/07 07:51 upstream 8ed710da2873 d88f3abb .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in path_openat
2022/12/04 12:19 upstream c2bf05db6c78 e080de16 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in path_openat
2022/12/01 14:24 upstream 04aa64375f48 4c2a66e8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in path_openat
2022/11/23 07:45 upstream eb7081409f94 9da37ae8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in path_openat
2023/04/18 03:30 upstream 6a8f57ae2eb0 436577a9 .config console log report info ci-qemu-upstream-386 general protection fault in path_openat
* Struck through repros no longer work on HEAD.