[moderation] [block?] BUG: unable to handle kernel paging request in loop_queue_rq

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 577490b6abb9 Merge branches 'for-next/core' and 'for-next/..
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=16842dc4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=5408fc4cf982e2c4
dashboard link: https://syzkaller.appspot.com/bug?extid=fe4d492cd56a40e65366
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
CC: [ax...@kernel.dk 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/f9a89a276c80/disk-577490b6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6c19133a4de5/vmlinux-577490b6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0dde1fa5fad3/Image-577490b6.gz.xz

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

Unable to handle kernel paging request at virtual address e4ff9fffe0001824
KASAN: maybe wild-memory-access in range [0x2800ffff0000c120-0x2800ffff0000c127]
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
[e4ff9fffe0001824] address between user and kernel address ranges
Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 UID: 0 PID: 7977 Comm: syz.6.308 Tainted: G W 6.13.0-rc6-syzkaller-g577490b6abb9 #0
Tainted: [W]=WARN
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/0x7904 kernel/locking/lockdep.c:5089
lr : lock_acquire+0x23c/0x724 kernel/locking/lockdep.c:5849
sp : ffff8000a3ec6e40
x29: ffff8000a3ec7100 x28: ffff8000803600c0 x27: 0000000000000000
x26: ffff0001b37e5500 x25: 0000000000000000 x24: 0000000000000001
x23: 0000000000000000 x22: 1ffff00011f320ca x21: 2800ffff0000c120
x20: 0000000000000001 x19: 0000000000000000 x18: ffff8000a3ec6fc0
x17: 000000000003fd64 x16: ffff8000832776d4 x15: 0000000000000001
x14: 1fffe00018211000 x13: dfff800000000000 x12: ffff7000147d8df0
x11: ffff800080466cdc x10: ffff80008f990650 x9 : 00000000000000f3
x8 : 05001fffe0001824 x7 : ffff8000803600c0 x6 : 0000000000000000
x5 : 0000000000000001 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000000 x1 : 0000000000000000 x0 : 2800ffff0000c120
Call trace:
__lock_acquire+0xfc/0x7904 kernel/locking/lockdep.c:5089 (P)
lock_acquire+0x23c/0x724 kernel/locking/lockdep.c:5849
__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]
loop_queue_work drivers/block/loop.c:893 [inline]
loop_queue_rq+0x974/0xadc drivers/block/loop.c:1876
__blk_mq_issue_directly block/blk-mq.c:2687 [inline]
blk_mq_request_issue_directly+0x2dc/0x5a0 block/blk-mq.c:2774
blk_mq_plug_issue_direct+0x264/0x548 block/blk-mq.c:2795
blk_mq_flush_plug_list+0x654/0x13ac block/blk-mq.c:2906
__blk_flush_plug+0x388/0x460 block/blk-core.c:1213
blk_finish_plug+0x68/0x90 block/blk-core.c:1240
btrfs_write_and_wait_transaction+0xec/0x1e8 fs/btrfs/transaction.c:1258
btrfs_commit_transaction+0x1ad0/0x2ba4 fs/btrfs/transaction.c:2519
btrfs_ioctl_subvol_setflags+0x4a8/0x6b4 fs/btrfs/ioctl.c:1528
btrfs_ioctl+0x60c/0xb04 fs/btrfs/ioctl.c:5194
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:906 [inline]
__se_sys_ioctl fs/ioctl.c:892 [inline]
__arm64_sys_ioctl+0x14c/0x1cc fs/ioctl.c:892
__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: d007a948 b9465108 340090a8 d343fea8 (386d6908)
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
0: d007a948 adrp x8, 0xf52a000
4: b9465108 ldr w8, [x8, #1616]
8: 340090a8 cbz w8, 0x121c
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.