[moderation] [btrfs?] BUG: unable to handle kernel paging request in btrfs_simple_end_io

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 1bf329c696cf Merge remote-tracking branch 'tip/irq/core' i..
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=132bd2a7980000
kernel config: https://syzkaller.appspot.com/x/.config?x=9bfadfb661dcd85e
dashboard link: https://syzkaller.appspot.com/bug?extid=6cc251d6f92b86755e8a
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
CC: [c...@fb.com dst...@suse.com jo...@toxicpanda.com linux...@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/ce371aa5cd38/disk-1bf329c6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d9b9cedf697e/vmlinux-1bf329c6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9376f54faf55/Image-1bf329c6.gz.xz

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

Unable to handle kernel paging request at virtual address 001f7fe000182113
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
[001f7fe000182113] address between user and kernel address ranges
Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 UID: 0 PID: 6670 Comm: syz.4.29 Not tainted 6.12.0-rc5-syzkaller-g1bf329c696cf #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 : ffff8000800076a0
x29: ffff800080007960 x28: ffff80008025a29c x27: 0000000000000000
x26: ffff0001b36384c0 x25: 0000000000000000 x24: 0000000000000001
x23: 0000000000000000 x22: 1ffff00011f000ba x21: 00ffff0000c10898
x20: 0000000000000001 x19: 0000000000000000 x18: 1fffe000366c7076
x17: ffff800123ee9000 x16: ffff8000830cb3ac x15: 0000000000000001
x14: 1fffe00018a68091 x13: dfff800000000000 x12: ffff700010000efc
x11: ffff80008035f828 x10: ffff80008f8005d4 x9 : 00000000000000f3
x8 : 001fffe000182113 x7 : ffff80008025a29c x6 : 0000000000000000
x5 : 0000000000000001 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000000 x1 : 0000000000000000 x0 : 00ffff0000c10898
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 include/linux/spinlock_api_smp.h:133 [inline]
_raw_spin_lock+0x48/0x60 kernel/locking/spinlock.c:154
__queue_work+0x8b0/0x1308
queue_work_on+0xe0/0x1a0 kernel/workqueue.c:2390
queue_work include/linux/workqueue.h:662 [inline]
btrfs_simple_end_io+0x32c/0x454 fs/btrfs/bio.c:367
bio_endio+0x82c/0x868 block/bio.c:1708
blk_update_request+0x4ac/0xda0 block/blk-mq.c:923
blk_mq_end_request+0x54/0x88 block/blk-mq.c:1051
lo_complete_rq+0x188/0x2f4 drivers/block/loop.c:386
blk_complete_reqs block/blk-mq.c:1126 [inline]
blk_done_softirq+0x11c/0x168 block/blk-mq.c:1131
handle_softirqs+0x2e0/0xbf8 kernel/softirq.c:554
__do_softirq+0x14/0x20 kernel/softirq.c:588
____do_softirq+0x14/0x20 arch/arm64/kernel/irq.c:81
call_on_irq_stack+0x24/0x4c arch/arm64/kernel/entry.S:891
do_softirq_own_stack+0x20/0x2c arch/arm64/kernel/irq.c:86
do_softirq+0x90/0xf8 kernel/softirq.c:455
__local_bh_enable_ip+0x288/0x44c kernel/softirq.c:382
local_bh_enable+0x28/0x34 include/linux/bottom_half.h:33
put_cpu_fpsimd_context arch/arm64/kernel/fpsimd.c:244 [inline]
fpsimd_restore_current_state+0x64/0xec arch/arm64/kernel/fpsimd.c:1810
do_notify_resume+0x114/0x1f4 arch/arm64/kernel/entry-common.c:154
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: b007a508 b945d508 34008c88 d343fea8 (386d6908)
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
0: b007a508 adrp x8, 0xf4a1000
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]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.