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: 95d, last: 3d03h
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 326d 322d 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 fcaa801fffe00039
KASAN: maybe wild-memory-access in range [0xe55800ffff0001c8-0xe55800ffff0001cf]
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
[fcaa801fffe00039] address between user and kernel address ranges
Internal error: Oops: 0000000096000004 [#1]  SMP
Modules linked in:
CPU: 0 UID: 0 PID: 6475 Comm: syz-executor Not tainted 6.15.0-rc2-syzkaller-gc72692105976 #0 PREEMPT 
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 : kasan_byte_accessible+0x10/0x20 mm/kasan/generic.c:199
lr : __kasan_check_byte+0x20/0x54 mm/kasan/common.c:556
sp : ffff8000a5387950
x29: ffff8000a5387950 x28: ffff80008ff31000 x27: ffff0000d940db80
x26: ffff80008b9ad5f4 x25: 0000000000000000 x24: 0000000000000001
x23: 0000000000000000 x22: e55800ffff0001cb x21: e55800ffff0001cb
x20: 0000000000000000 x19: ffff80008b9ad5f4 x18: 1fffe000366ddeb6
x17: ffff80008ff2e000 x16: ffff80008333712c x15: 0000000000000001
x14: 1fffe000366e0899 x13: ffff8000a5388000 x12: ffff8000a5387a40
x11: ffff8000a5387a60 x10: 0000000000000003 x9 : 1cab001fffe00039
x8 : dfff800000000000 x7 : ffff80008039f480 x6 : ffff8000803777c8
x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000000 x1 : ffff80008b9ad5f4 x0 : e55800ffff0001cb
Call trace:
 kasan_mem_to_shadow include/linux/kasan.h:64 [inline] (P)
 kasan_byte_accessible+0x10/0x20 mm/kasan/generic.c:199 (P)
 kasan_check_byte include/linux/kasan.h:399 [inline]
 lock_acquire+0xb4/0x2e8 kernel/locking/lockdep.c:5840
 __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:612 [inline]
 bch2_fs_release+0x5f4/0x720 fs/bcachefs/super.c:627
 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+0x314/0x384 fs/bcachefs/super.c:690
 bch2_kill_sb+0x48/0x58 fs/bcachefs/fs.c:2304
 deactivate_locked_super+0xc4/0x12c fs/super.c:473
 deactivate_super+0xe0/0x100 fs/super.c:506
 cleanup_mnt+0x34c/0x3dc fs/namespace.c:1435
 __cleanup_mnt+0x20/0x30 fs/namespace.c:1442
 task_work_run+0x230/0x2e0 kernel/task_work.c:227
 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
 do_notify_resume+0x178/0x1f4 arch/arm64/kernel/entry-common.c:151
 exit_to_user_mode_prepare arch/arm64/kernel/entry-common.c:169 [inline]
 exit_to_user_mode arch/arm64/kernel/entry-common.c:178 [inline]
 el0_svc+0xac/0x168 arch/arm64/kernel/entry-common.c:745
 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: d503245f d2d00008 d343fc09 f2fbffe8 (38686928) 
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
   0:	d503245f 	bti	c
   4:	d2d00008 	mov	x8, #0x800000000000        	// #140737488355328
   8:	d343fc09 	lsr	x9, x0, #3
   c:	f2fbffe8 	movk	x8, #0xdfff, lsl #48
* 10:	38686928 	ldrb	w8, [x9, x8] <-- trapping instruction

Crashes (6):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/04/23 05:01 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci c72692105976 53a8b9bd .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/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.