syzbot


Internal error in fault_in_writeable

Status: upstream: reported on 2025/08/12 07:47
Reported-by: syzbot+6ea090b57a4a81675d17@syzkaller.appspotmail.com
First crash: 4d13h, last: 17h30m

Sample crash report:
BTRFS info (device loop1): enabling ssd optimizations
Internal error: Oops - BTI: 0000000036000001 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 4195 Comm: syz.1.13 Not tainted 5.15.189-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/30/2025
pstate: 42400405 (nZcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=jc)
pc : fault_in_writeable+0x254/0x324 mm/gup.c:1721
lr : fault_in_writeable+0x234/0x324 mm/gup.c:1721
sp : ffff8000201779b0
x29: ffff8000201779c0 x28: 0000002100000000 x27: 0000000021002000
x26: 0000000021000000 x25: 0000000021000000 x24: 00000000fffffff2
x23: 1fffe00019fb2368 x22: ffff0000cfd91b40 x21: 0000000000000000
x20: 0000000021000000 x19: dfff800000000000 x18: 0000000000000000
x17: 0000000000000002 x16: ffff800008733858 x15: 000000000000000a
x14: 0000000000ff0100 x13: 1ffff0000282e06b x12: 0000000000ff0100
x11: 0000000000000000 x10: 0000000000000002 x9 : 0000ffffffffffff
x8 : 0000000021000000 x7 : ffff800008750ed4 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000001
x2 : 0000000000000008 x1 : 0000000000000001 x0 : 0000000000000000
Call trace:
 fault_in_writeable+0x254/0x324 mm/gup.c:1721
 search_ioctl+0x348/0x4d8 fs/btrfs/ioctl.c:2278
 btrfs_ioctl_tree_search_v2+0x244/0x4f8 fs/btrfs/ioctl.c:2362
 btrfs_ioctl+0x2c4/0xb38 fs/btrfs/ioctl.c:4975
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:874 [inline]
 __se_sys_ioctl fs/ioctl.c:860 [inline]
 __arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:860
 __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+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
 el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: d503229f 2a1503f8 2a1503e0 38000915 (2a1803e1) 
---[ end trace 3205572830adc8a9 ]---
----------------
Code disassembly (best guess):
   0:	d503229f 	csdb
   4:	2a1503f8 	mov	w24, w21
   8:	2a1503e0 	mov	w0, w21
   c:	38000915 	sttrb	w21, [x8]
* 10:	2a1803e1 	mov	w1, w24 <-- trapping instruction

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/08/16 03:25 linux-5.15.y c79648372d02 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 Internal error in fault_in_writeable
2025/08/16 03:23 linux-5.15.y c79648372d02 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 Internal error in fault_in_writeable
2025/08/12 07:47 linux-5.15.y c79648372d02 c06e8995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 Internal error in fault_in_writeable
2025/08/12 07:46 linux-5.15.y c79648372d02 c06e8995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 Internal error in fault_in_writeable
* Struck through repros no longer work on HEAD.