syzbot

 sign-in | mailing list | source | docs
🐞 Open [706]
🐞 Fixed [58]
🐞 Invalid [596]
⬇ Missing Backports [56]
≡ Crashes
Kernel Health Bugs/Month Bug Lifetimes Fuzzing
💬 Send us feedback

BUG: unable to handle kernel paging request in mark_buffer_dirty_inode

Status: upstream: reported C repro on 2024/05/27 20:45
Bug presence: origin:lts-only
[Documentation on labels]
Reported-by: syzbot+fc442b8ed38e8166f382@syzkaller.appspotmail.com
First crash: 177d, last: 38d
Fix bisection: failed (error log, bisect log)
  
▶ ▼ Bug presence (2)
Date Name Commit Repro Result
2024/05/28 linux-5.15.y (ToT) c61bd26ae81a C [report] BUG: unable to handle kernel paging request in mark_buffer_dirty_inode
2024/05/28 upstream (ToT) 2bfcfd584ff5 C Didn't crash
▶ ▼ Similar bugs (5)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 general protection fault in mark_buffer_dirty_inode 1 216d 216d 0/3 auto-obsoleted due to no activity on 2024/07/28 10:58
android-6-1 KASAN: null-ptr-deref Write in mark_buffer_dirty_inode 1 45d 45d 0/2 premoderation: reported on 2024/10/07 16:44
linux-4.19 general protection fault in mark_buffer_dirty_inode (2) C error 1 724d 724d 0/1 upstream: reported C repro on 2022/11/28 03:52
upstream general protection fault in mark_buffer_dirty_inode (2) udf C 32 565d 723d 22/28 fixed on 2023/06/08 14:41
android-54 KASAN: null-ptr-deref Write in mark_buffer_dirty_inode fat 1 658d 658d 0/2 auto-obsoleted due to no activity on 2023/06/02 15:38
▶ ▼ Last patch testing requests (1)
Created Duration User Patch Repo Result
2024/10/14 02:10 11m retest repro linux-5.15.y report log
▶ ▼ Fix bisection attempts (4)
Created Duration User Patch Repo Result
2024/11/03 04:51 2m fix candidate upstream error job log
2024/08/11 16:42 49m fix candidate upstream error job log
2024/07/07 14:58 1m fix candidate upstream error job log
2024/07/07 03:00 41m bisect fix linux-5.15.y error job log

Sample crash report:
Unable to handle kernel paging request at virtual address dfff800000000002
Mem abort info:
  ESR = 0x0000000096000006
  EC = 0x25: DABT (current EL), IL = 32 bits
  SET = 0, FnV = 0
  EA = 0, S1PTW = 0
  FSC = 0x06: level 2 translation fault
Data abort info:
  ISV = 0, ISS = 0x00000006
  CM = 0, WnR = 0
[dfff800000000002] address between user and kernel address ranges
Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 4014 Comm: syz-executor294 Not tainted 5.15.160-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : mark_buffer_dirty_inode+0x5c/0x290 fs/buffer.c:573
lr : mark_buffer_dirty_inode+0x38/0x290 fs/buffer.c:571
sp : ffff80001cbe75b0
x29: ffff80001cbe75c0 x28: ffff0000d9e50000 x27: ffff0000df185060
x26: dfff800000000000 x25: 1ffff0000397cf00 x24: 0000000000000000
x23: ffff70000397ced8 x22: ffff0000df184d20 x21: 0000000000000010
x20: ffff0000df184e68 x19: 0000000000000000 x18: 0000000000000000
x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000
x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000
x11: 0000000000000000 x10: 0000000000000000 x9 : ffff0000c2379b40
x8 : 0000000000000002 x7 : 00000000376eac80 x6 : 000000000000007b
x5 : ffff0000df184858 x4 : ffff0000df184848 x3 : ffff80000985f9f4
x2 : 0000000000000018 x1 : ffff0000df184e38 x0 : 0000000000000000
Call trace:
 mark_buffer_dirty_inode+0x5c/0x290 fs/buffer.c:573
 udf_rename+0xb50/0x10b0 fs/udf/namei.c:1190
 vfs_rename+0xac8/0xe04 fs/namei.c:4832
 do_renameat2+0xa00/0x10c0 fs/namei.c:4985
 __do_sys_renameat2 fs/namei.c:5018 [inline]
 __se_sys_renameat2 fs/namei.c:5015 [inline]
 __arm64_sys_renameat2+0xe0/0xfc fs/namei.c:5015
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
 el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
 el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: 97f97c91 91004275 f940029b d343fea8 (387a6908) 
---[ end trace 838a5793ae6d26c9 ]---
----------------
Code disassembly (best guess):
   0:	97f97c91 	bl	0xffffffffffe5f244
   4:	91004275 	add	x21, x19, #0x10
   8:	f940029b 	ldr	x27, [x20]
   c:	d343fea8 	lsr	x8, x21, #3
* 10:	387a6908 	ldrb	w8, [x8, x26] <-- trapping instruction

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/05/27 23:13 linux-5.15.y c61bd26ae81a 761766e6 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in mark_buffer_dirty_inode
2024/05/27 20:44 linux-5.15.y c61bd26ae81a 761766e6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in mark_buffer_dirty_inode
* Struck through repros no longer work on HEAD.