[moderation] [xfs?] BUG: unable to handle kernel paging request in xlog_bio_end_io

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 2e7aff49b5da 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=11b627e8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=696fb014d05da3a3
dashboard link: https://syzkaller.appspot.com/bug?extid=a821191a6509052820fa
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
CC: [c...@kernel.org chanda...@oracle.com djw...@kernel.org linux-...@vger.kernel.org linu...@vger.kernel.org]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ef408f67fde3/disk-2e7aff49.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/414ac17a20dc/vmlinux-2e7aff49.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a93415d2a7e7/Image-2e7aff49.gz.xz

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

Unable to handle kernel paging request at virtual address 0009cb001fffe003
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
[0009cb001fffe003] address between user and kernel address ranges
Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 UID: 0 PID: 16 Comm: ksoftirqd/0 Not tainted 6.13.0-rc2-syzkaller-g2e7aff49b5da #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/0x7904 kernel/locking/lockdep.c:5089
lr : lock_acquire+0x23c/0x724 kernel/locking/lockdep.c:5849
sp : ffff800097a872e0
x29: ffff800097a875a0 x28: ffff80008035e56c x27: 0000000000000000
x26: ffff0001b360b500 x25: 0000000000000000 x24: 0000000000000001
x23: 0000000000000000 x22: 1ffff00011f300ca x21: d0525800ffff0019
x20: 0000000000000001 x19: 0000000000000000 x18: 1fffe000366c167e
x17: ffff80008f97d000 x16: ffff80008326d65c x15: 0000000000000001
x14: 1fffe0001dfa102d x13: dfff800000000000 x12: ffff700012f50e84
x11: ffff8000804648c0 x10: ffff80008f980650 x9 : 00000000000000f3
x8 : 1a0a4b001fffe003 x7 : ffff80008035e56c x6 : 0000000000000000
x5 : 0000000000000001 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000000 x1 : 0000000000000000 x0 : d0525800ffff0019
Call trace:
__lock_acquire+0xfc/0x7904 kernel/locking/lockdep.c:5089 (P)
lock_acquire+0x23c/0x724 kernel/locking/lockdep.c:5849 (L)
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]
xlog_bio_end_io+0x84/0x98 fs/xfs/xfs_log.c:1605
bio_endio+0x840/0x87c block/bio.c:1645
blk_update_request+0x4ac/0xda0 block/blk-mq.c:981
blk_mq_end_request+0x54/0x88 block/blk-mq.c:1143
blk_flush_complete_seq+0x58c/0xaf4 block/blk-flush.c:191
flush_end_io+0x9f0/0xd68 block/blk-flush.c:250
__blk_mq_end_request+0x3b4/0x558 block/blk-mq.c:1133
blk_mq_end_request+0x68/0x88 block/blk-mq.c:1145
lo_complete_rq+0x188/0x2f4 drivers/block/loop.c:386
blk_complete_reqs block/blk-mq.c:1218 [inline]
blk_done_softirq+0x11c/0x168 block/blk-mq.c:1223
handle_softirqs+0x320/0xd34 kernel/softirq.c:554
run_ksoftirqd+0x70/0xc0 kernel/softirq.c:943
smpboot_thread_fn+0x4b0/0x90c kernel/smpboot.c:164
kthread+0x288/0x310 kernel/kthread.c:389
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:862
Code: 9007a8e8 b9465108 340090a8 d343fea8 (386d6908)
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
0: 9007a8e8 adrp x8, 0xf51c000
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.