syzbot


BUG: unable to handle kernel paging request in bch2_fs_release

Status: upstream: reported on 2025/04/03 17:46
Subsystems: bcachefs
[Documentation on labels]
Reported-by: syzbot+d35395c659ed8030c05d@syzkaller.appspotmail.com
First crash: 76d, last: 3d22h
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [bcachefs?] BUG: unable to handle kernel paging request in bch2_fs_release 0 (1) 2025/04/03 17:46
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream general protection fault in bch2_fs_release bcachefs 1 307d 303d 0/28 auto-obsoleted due to no activity on 2024/09/01 18:19

Sample crash report:
Unable to handle kernel paging request at virtual address e1ff9fffe0001864
KASAN: maybe wild-memory-access in range [0x1000ffff0000c320-0x1000ffff0000c327]
Mem abort info:
  ESR = 0x0000000096000004
  EC = 0x25: DABT (current EL), IL = 32 bits
  SET = 0, FnV = 0
  EA = 0, S1PTW = 0
  FSC = 0x04: level 0 translation fault
Data abort info:
  ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000
  CM = 0, WnR = 0, TnD = 0, TagAccess = 0
  GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0
[e1ff9fffe0001864] address between user and kernel address ranges
Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 UID: 0 PID: 6672 Comm: syz.4.10 Not tainted 6.14.0-syzkaller-gd6b13dbd03b7 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
pstate: 804000c5 (Nzcv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __lock_acquire+0xfc/0x7904 kernel/locking/lockdep.c:5091
lr : lock_acquire+0x23c/0x724 kernel/locking/lockdep.c:5851
sp : ffff8000a46769a0
x29: ffff8000a4676c60 x28: ffff80008036e1e8 x27: 0000000000000000
x26: ffff0001b3737540 x25: 0000000000000000 x24: 0000000000000001
x23: 0000000000000000 x22: 1ffff00011faa0cd x21: 1000ffff0000c322
x20: 0000000000000001 x19: 0000000000000000 x18: 1fffe000366e6e86
x17: ffff80008fd4d000 x16: ffff8000832bccd4 x15: 0000000000000001
x14: 1ffff00011faa0cd x13: dfff800000000000 x12: ffff7000148ced5c
x11: ffff80008046f030 x10: ffff80008fd50668 x9 : 00000000000000f3
x8 : 02001fffe0001864 x7 : ffff80008036e1e8 x6 : 0000000000000000
x5 : 0000000000000001 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000000 x1 : 0000000000000000 x0 : 1000ffff0000c322
Call trace:
 __lock_acquire+0xfc/0x7904 kernel/locking/lockdep.c:5091 (P)
 lock_acquire+0x23c/0x724 kernel/locking/lockdep.c:5851
 __raw_spin_lock_irq include/linux/spinlock_api_smp.h:119 [inline]
 _raw_spin_lock_irq+0x58/0x70 kernel/locking/spinlock.c:170
 put_pwq_unlocked kernel/workqueue.c:1662 [inline]
 destroy_workqueue+0x8d8/0xdc0 kernel/workqueue.c:5911
 __bch2_fs_free fs/bcachefs/super.c:613 [inline]
 bch2_fs_release+0x64c/0x708 fs/bcachefs/super.c:624
 kobject_cleanup lib/kobject.c:689 [inline]
 kobject_release lib/kobject.c:720 [inline]
 kref_put include/linux/kref.h:65 [inline]
 kobject_put+0x2a8/0x41c lib/kobject.c:737
 bch2_fs_free+0x2c4/0x334 fs/bcachefs/super.c:686
 bch2_fs_alloc fs/bcachefs/super.c:963 [inline]
 bch2_fs_open+0x18ac/0x299c fs/bcachefs/super.c:2065
 bch2_fs_get_tree+0x58c/0x11d4 fs/bcachefs/fs.c:2190
 vfs_get_tree+0x90/0x28c fs/super.c:1814
 do_new_mount+0x278/0x900 fs/namespace.c:3560
 path_mount+0x590/0xe04 fs/namespace.c:3887
 do_mount fs/namespace.c:3900 [inline]
 __do_sys_mount fs/namespace.c:4111 [inline]
 __se_sys_mount fs/namespace.c:4088 [inline]
 __arm64_sys_mount+0x4f4/0x5d0 fs/namespace.c:4088
 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
 invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49
 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132
 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151
 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:744
 el0t_64_sync_handler+0x84/0x108 arch/arm64/kernel/entry-common.c:762
 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600
Code: b007c708 b9466908 340090a8 d343fea8 (386d6908) 
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
   0:	b007c708 	adrp	x8, 0xf8e1000
   4:	b9466908 	ldr	w8, [x8, #1640]
   8:	340090a8 	cbz	w8, 0x121c
   c:	d343fea8 	lsr	x8, x21, #3
* 10:	386d6908 	ldrb	w8, [x8, x13] <-- trapping instruction

Crashes (5):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/04/03 17:45 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci d6b13dbd03b7 996a9618 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 BUG: unable to handle kernel paging request in bch2_fs_release
2025/03/22 10:10 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci a2392f333575 c6512ef7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 BUG: unable to handle kernel paging request in bch2_fs_release
2025/02/23 09:01 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci a1c24ab82279 d34966d1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 BUG: unable to handle kernel paging request in bch2_fs_release
2025/01/20 23:52 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 1950a0af2d55 6e87cfa2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 BUG: unable to handle kernel paging request in bch2_fs_release
2025/01/20 23:51 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 1950a0af2d55 6e87cfa2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 BUG: unable to handle kernel paging request in bch2_fs_release
* Struck through repros no longer work on HEAD.