syzbot


BUG: unable to handle kernel paging request in write_all_supers

Status: upstream: reported C repro on 2024/10/04 18:21
Bug presence: origin:upstream
[Documentation on labels]
Reported-by: syzbot+c3386017aa36dd22437b@syzkaller.appspotmail.com
First crash: 18d, last: 3d06h
Bug presence (1)
Date Name Commit Repro Result
2024/10/17 upstream (ToT) c964ced77262 C [report] BUG: MAX_LOCKDEP_KEYS too low!
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream general protection fault in write_all_supers btrfs C 20 6h09m 41d 0/28 upstream: reported C repro on 2024/09/10 22:11
Last patch testing requests (3)
Created Duration User Patch Repo Result
2024/10/19 13:38 17m retest repro linux-5.15.y report log
2024/10/19 13:38 17m retest repro linux-5.15.y report log
2024/10/19 13:38 16m retest repro linux-5.15.y report log

Sample crash report:
BTRFS info (device loop0): using spread ssd allocation scheme
BTRFS info (device loop0): disk space caching is enabled
BTRFS info (device loop0): has skinny extents
BTRFS error (device loop0): ignoredatacsums must be used with ro mount option
Unable to handle kernel paging request at virtual address dfff800000000000
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
[dfff800000000000] address between user and kernel address ranges
Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 4015 Comm: syz-executor588 Not tainted 5.15.167-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : backup_super_roots fs/btrfs/disk-io.c:2007 [inline]
pc : write_all_supers+0xee0/0x3a6c fs/btrfs/disk-io.c:4154
lr : lowmem_page_address include/linux/mm.h:1612 [inline]
lr : btrfs_header_level fs/btrfs/ctree.h:2194 [inline]
lr : backup_super_roots fs/btrfs/disk-io.c:2005 [inline]
lr : write_all_supers+0xdf4/0x3a6c fs/btrfs/disk-io.c:4154
sp : ffff80001d0d7200
x29: ffff80001d0d75c0 x28: 1ffff00002892b23 x27: 0000000000000009
x26: ffff0000d71deb2b x25: dfff800000000000 x24: 0000000000000000
x23: 0000000000000000 x22: dfff800000000000 x21: 1fffe00019037808
x20: 0000000000000000 x19: ffff0000c81bc040 x18: ffff80001d0d72a0
x17: 0000000000000000 x16: ffff80000824ecc0 x15: 000000000000c5f7
x14: 0000000069e97732 x13: 0000000000000000 x12: 0000000000000003
x11: 0000000000000000 x10: 1fffe000193a6ee8 x9 : ffff0000c81bc000
x8 : 0000000000000000 x7 : 0000000000000000 x6 : 000000000000003f
x5 : 0000000000000040 x4 : ffffffffffffffd0 x3 : 0000000000000010
x2 : 0000000000000003 x1 : 0000000000000000 x0 : ffff0000c9d37860
Call trace:
 backup_super_roots fs/btrfs/disk-io.c:2007 [inline]
 write_all_supers+0xee0/0x3a6c fs/btrfs/disk-io.c:4154
 btrfs_commit_transaction+0x1694/0x30f0 fs/btrfs/transaction.c:2462
 btrfs_set_free_space_cache_v1_active+0x78/0x280 fs/btrfs/free-space-cache.c:4001
 btrfs_remount_cleanup fs/btrfs/super.c:1914 [inline]
 btrfs_remount+0x644/0x130c fs/btrfs/super.c:2117
 legacy_reconfigure+0xfc/0x114 fs/fs_context.c:634
 reconfigure_super+0x1d0/0x6ec fs/super.c:936
 do_remount fs/namespace.c:2661 [inline]
 path_mount+0xbec/0x101c fs/namespace.c:3327
 do_mount fs/namespace.c:3348 [inline]
 __do_sys_mount fs/namespace.c:3556 [inline]
 __se_sys_mount fs/namespace.c:3533 [inline]
 __arm64_sys_mount+0x510/0x5e0 fs/namespace.c:3533
 __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: aa1303e0 97a2b989 f9400274 d343fe88 (38796908) 
---[ end trace 8728c1b8e8724c0f ]---
----------------
Code disassembly (best guess):
   0:	aa1303e0 	mov	x0, x19
   4:	97a2b989 	bl	0xfffffffffe8ae628
   8:	f9400274 	ldr	x20, [x19]
   c:	d343fe88 	lsr	x8, x20, #3
* 10:	38796908 	ldrb	w8, [x8, x25] <-- trapping instruction

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/10/04 20:19 linux-5.15.y 3a5928702e71 d7906eff .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 write_all_supers
2024/10/04 19:41 linux-5.15.y 3a5928702e71 d7906eff .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 write_all_supers
2024/10/04 19:02 linux-5.15.y 3a5928702e71 d7906eff .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 write_all_supers
2024/10/04 18:20 linux-5.15.y 3a5928702e71 d7906eff .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in write_all_supers
* Struck through repros no longer work on HEAD.