[moderation] [bcachefs?] BUG: unable to handle kernel paging request in bch2_fs_btree_interior_update_exit

5 views
Skip to first unread message

syzbot

unread,
Nov 18, 2024, 4:30:34 PM11/18/24
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 887407160d72 Merge remote-tracking branch 'iommu/arm/smmu'..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=118ad1a7980000
kernel config: https://syzkaller.appspot.com/x/.config?x=a1eb85a42cb8ccec
dashboard link: https://syzkaller.appspot.com/bug?extid=bb30490bf31345f926c5
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
CC: [kent.ov...@linux.dev linux-b...@vger.kernel.org linux-...@vger.kernel.org]

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1011f7c2c68d/disk-88740716.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9035dac2e5ad/vmlinux-88740716.xz
kernel image: https://storage.googleapis.com/syzbot-assets/55be49953149/Image-88740716.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+bb3049...@syzkaller.appspotmail.com

Unable to handle kernel paging request at virtual address 0021fe001fffe003
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
[0021fe001fffe003] address between user and kernel address ranges
Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 UID: 0 PID: 6427 Comm: syz-executor Not tainted 6.12.0-rc7-syzkaller-g887407160d72 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
pstate: 804000c5 (Nzcv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __lock_acquire+0xfc/0x77c8 kernel/locking/lockdep.c:5065
lr : lock_acquire+0x240/0x728 kernel/locking/lockdep.c:5825
sp : ffff8000a45c7580
x29: ffff8000a45c7840 x28: ffff80008025d2e8 x27: 0000000000000000
x26: ffff0001b365a4c0 x25: 0000000000000000 x24: 0000000000000001
x23: 0000000000000000 x22: 1ffff00011f020ba x21: d913f000ffff0018
x20: 0000000000000001 x19: 0000000000000000 x18: 1fffe000366cb476
x17: ffff80008f80d000 x16: ffff8000830ce3b0 x15: 0000000000000001
x14: 1fffe00018211000 x13: dfff800000000000 x12: ffff7000148b8ed8
x11: ffff800080359554 x10: ffff80008f8105d4 x9 : 00000000000000f3
x8 : 1b227e001fffe003 x7 : ffff80008025d2e8 x6 : 0000000000000000
x5 : 0000000000000001 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000000 x1 : 0000000000000000 x0 : d913f000ffff0018
Call trace:
__lock_acquire+0xfc/0x77c8 kernel/locking/lockdep.c:5065 (P)
lock_acquire+0x240/0x728 kernel/locking/lockdep.c:5825 (L)
lock_acquire+0x240/0x728 kernel/locking/lockdep.c:5825
__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:5883
bch2_fs_btree_interior_update_exit+0x8c/0xb4 fs/bcachefs/btree_update_interior.c:2682
__bch2_fs_free fs/bcachefs/super.c:554 [inline]
bch2_fs_release+0x1f0/0x728 fs/bcachefs/super.c:610
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:672
bch2_kill_sb+0x48/0x58 fs/bcachefs/fs.c:2279
deactivate_locked_super+0xc4/0x12c fs/super.c:473
deactivate_super+0xe0/0x100 fs/super.c:506
cleanup_mnt+0x34c/0x3dc fs/namespace.c:1373
__cleanup_mnt+0x20/0x30 fs/namespace.c:1380
task_work_run+0x230/0x2e0 kernel/task_work.c:239
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: f007a5a8 b945d508 34008c88 d343fea8 (386d6908)
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
0: f007a5a8 adrp x8, 0xf4b7000
4: b945d508 ldr w8, [x8, #1492]
8: 34008c88 cbz w8, 0x1198
c: d343fea8 lsr x8, x21, #3
* 10: 386d6908 ldrb w8, [x8, x13] <-- trapping instruction


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

syzbot

unread,
Feb 12, 2025, 4:24:11 PM2/12/25
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages