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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 526116b79e8c KVM: arm64: Shave a few bytes from the EL2 id..
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=177750a7980000
kernel config: https://syzkaller.appspot.com/x/.config?x=e39b0b4b1ace5bc0
dashboard link: https://syzkaller.appspot.com/bug?extid=e288713f016ba9a2fd9b
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/2f7b2b08fdad/disk-526116b7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b69595b63015/vmlinux-526116b7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/39fd415ada60/Image-526116b7.gz.xz

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

Unable to handle kernel paging request at virtual address 001f7fe000366ca1
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
[001f7fe000366ca1] address between user and kernel address ranges
Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 UID: 0 PID: 5361 Comm: kworker/u8:8 Not tainted 6.12.0-rc4-syzkaller-g526116b79e8c #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Workqueue: bat_events batadv_nc_worker
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 : ffff8000800076c0
x29: ffff800080007980 x28: ffff800080258a9c x27: 0000000000000000
x26: ffff0001b363a4c0 x25: 0000000000000000 x24: 0000000000000001
x23: 0000000000000000 x22: 1ffff00011f000ba x21: 00ffff0001b36508
x20: 0000000000000001 x19: 0000000000000000 x18: ffff80009f967788
x17: ffff800123eeb000 x16: ffff8000830c7d0c x15: 0000000000000001
x14: 1fffe0001ddf1e42 x13: dfff800000000000 x12: ffff700010000f00
x11: ffff80008035e028 x10: ffff80008f8005d4 x9 : 00000000000000f3
x8 : 001fffe000366ca1 x7 : ffff800080258a9c x6 : 0000000000000000
x5 : 0000000000000001 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000000 x1 : 0000000000000000 x0 : 00ffff0001b36508
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]
xfs_buf_ioend_async fs/xfs/xfs_buf.c:1435 [inline]
xfs_buf_bio_end_io+0x1c4/0x250 fs/xfs/xfs_buf.c:1519
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
__raw_spin_unlock_bh include/linux/spinlock_api_smp.h:167 [inline]
_raw_spin_unlock_bh+0x3c/0x4c kernel/locking/spinlock.c:210
spin_unlock_bh include/linux/spinlock.h:396 [inline]
batadv_nc_purge_paths+0x2f4/0x378 net/batman-adv/network-coding.c:471
batadv_nc_worker+0x2e4/0x580 net/batman-adv/network-coding.c:720
process_one_work+0x7bc/0x1600 kernel/workqueue.c:3229
process_scheduled_works kernel/workqueue.c:3310 [inline]
worker_thread+0x97c/0xeec kernel/workqueue.c:3391
kthread+0x288/0x310 kernel/kthread.c:389
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:862
Code: d007a508 b945d508 34008c88 d343fea8 (386d6908)
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
0: d007a508 adrp x8, 0xf4a2000
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.