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

Hello,

syzbot found the following issue on:

HEAD commit: 14d05f12084d Merge remote-tracking branch 'will/for-next/p..
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=16374078580000
kernel config: https://syzkaller.appspot.com/x/.config?x=afb3000d0159783f
dashboard link: https://syzkaller.appspot.com/bug?extid=4a601607f57eb52a820c
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
CC: [[email protected] [email protected] [email protected] [email protected]]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c2532c9b9fcd/disk-14d05f12.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9b4767367f2c/vmlinux-14d05f12.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9b1822d165d0/Image-14d05f12.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: [email protected]

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: 1 UID: 0 PID: 6894 Comm: syz.2.72 Not tainted 6.14.0-rc5-syzkaller-g14d05f12084d #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
pstate: 804000c5 (Nzcv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __lock_acquire+0xfc/0x7904 kernel/locking/lockdep.c:5091
lr : lock_acquire+0x23c/0x724 kernel/locking/lockdep.c:5851
sp : ffff80009bb16780
x29: ffff80009bb16a40 x28: ffff80008036313c x27: 0000000000000000
x26: ffff0001b37b0540 x25: 0000000000000000 x24: 0000000000000001
x23: 0000000000000000 x22: 1ffff00011f780cb x21: 00ffff0000c10898
x20: 0000000000000001 x19: 0000000000000000 x18: 1fffe0001b68ad33
x17: 0000000000027abd x16: ffff8000832b8f3c x15: 0000000000000001
x14: 1fffe0001b27f41b x13: dfff800000000000 x12: ffff700013762d18
x11: ffff80008046d19c x10: ffff80008fbc0658 x9 : 00000000000000f3
x8 : 001fffe000182113 x7 : ffff80008036313c x6 : 0000000000000000
x5 : 0000000000000001 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000000 x1 : 0000000000000000 x0 : 00ffff0000c10898
Call trace:
__lock_acquire+0xfc/0x7904 kernel/locking/lockdep.c:5091 (P)
lock_acquire+0x23c/0x724 kernel/locking/lockdep.c:5851
__raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline]
_raw_spin_lock+0x48/0x60 kernel/locking/spinlock.c:154
__queue_work+0x8d4/0x1324
queue_work_on+0xe0/0x1a0 kernel/workqueue.c:2392
queue_work include/linux/workqueue.h:662 [inline]
xlog_cil_push_now fs/xfs/xfs_log_cil.c:1667 [inline]
xlog_cil_force_seq+0x24c/0x638 fs/xfs/xfs_log_cil.c:1845
xfs_log_force_seq+0x1b8/0x4b0 fs/xfs/xfs_log.c:3097
__xfs_trans_commit+0x778/0xcb4 fs/xfs/xfs_trans.c:905
xfs_trans_roll+0x14c/0x4fc fs/xfs/xfs_trans.c:1058
xfs_defer_trans_roll+0x1ec/0x6ec fs/xfs/libxfs/xfs_defer.c:479
xfs_defer_finish_noroll+0x8d0/0x156c fs/xfs/libxfs/xfs_defer.c:688
xfs_trans_commit+0x154/0x228 fs/xfs/xfs_trans.c:947
xfs_attr_set+0xc80/0x1178 fs/xfs/libxfs/xfs_attr.c:1150
xfs_attr_change+0x254/0x334 fs/xfs/xfs_xattr.c:128
xfs_xattr_set+0x198/0x2cc fs/xfs/xfs_xattr.c:186
__vfs_setxattr+0x3d8/0x400 fs/xattr.c:200
__vfs_setxattr_noperm+0x110/0x578 fs/xattr.c:234
__vfs_setxattr_locked+0x1ec/0x218 fs/xattr.c:295
vfs_setxattr+0x1a8/0x344 fs/xattr.c:321
do_setxattr fs/xattr.c:636 [inline]
filename_setxattr+0x268/0x3fc fs/xattr.c:665
path_setxattrat+0x370/0x41c fs/xattr.c:713
__do_sys_setxattr fs/xattr.c:747 [inline]
__se_sys_setxattr fs/xattr.c:743 [inline]
__arm64_sys_setxattr+0xc0/0xdc fs/xattr.c:743
__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: f007ba88 b9465908 340090a8 d343fea8 (386d6908)
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
0: f007ba88 adrp x8, 0xf753000
4: b9465908 ldr w8, [x8, #1624]
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 [email protected].

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