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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: a5541c0811a0 Merge branch 'for-next/core' into for-kernelci
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=163d572a480000
kernel config: https://syzkaller.appspot.com/x/.config?x=cbd4e584773e9397
dashboard link: https://syzkaller.appspot.com/bug?extid=0f7fadd838dc39a7cf3f
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
CC: [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/4b7702208fb9/disk-a5541c08.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9ec0153ec051/vmlinux-a5541c08.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6f8725ad290a/Image-a5541c08.gz.xz

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

XFS (loop1): Filesystem has been shut down due to log error (0x2).
XFS (loop1): Please unmount the filesystem and rectify the problem(s).
Unable to handle kernel paging request at virtual address dead4ead00000000
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
CM = 0, WnR = 0
[dead4ead00000000] address between user and kernel address ranges
Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 77 Comm: kworker/1:1H Not tainted 6.1.0-rc8-syzkaller-33330-ga5541c0811a0 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Workqueue: xfs-log/loop1 xlog_ioend_work
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : xfs_trans_committed_bulk+0xf0/0x460 fs/xfs/xfs_trans.c:785
lr : arch_set_bit include/asm-generic/bitops/atomic.h:18 [inline]
lr : set_bit include/asm-generic/bitops/instrumented-atomic.h:29 [inline]
lr : xfs_trans_committed_bulk+0xd4/0x460 fs/xfs/xfs_trans.c:783
sp : ffff80000f76ba60
x29: ffff80000f76bba0 x28: ffff00011cdb4040 x27: 0000000000000001
x26: 0000000100000000 x25: ffff0000c4c1a330 x24: ffff00011cdb4000
x23: ffff00011ccc9c58 x22: 0000000000000001 x21: dead4ead00000000
x20: 0000000100000000 x19: ffff000128f14a80 x18: 00000000000000c0
x17: ffff80000dda8198 x16: ffff80000dbe6158 x15: ffff0000c0f43480
x14: 0000000000000000 x13: 00000000ffffffff x12: ffff0000c0f43480
x11: ff80800008e9f600 x10: 0000000000000000 x9 : 0000000000000002
x8 : ffff0000c4c1a370 x7 : ffff8000095d6a64 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000006 x1 : ffff80000ceb269e x0 : 0000000000000000
Call trace:
xfs_trans_committed_bulk+0xf0/0x460 fs/xfs/xfs_trans.c:785
xlog_cil_committed+0xcc/0x340 fs/xfs/xfs_log_cil.c:795
xlog_cil_process_committed+0x6c/0xa8 fs/xfs/xfs_log_cil.c:823
xlog_state_shutdown_callbacks+0xac/0x140 fs/xfs/xfs_log.c:538
xlog_force_shutdown+0x1ac/0x230 fs/xfs/xfs_log.c:3821
xlog_ioend_work+0x68/0xa0 fs/xfs/xfs_log.c:1402
process_one_work+0x2d8/0x504 kernel/workqueue.c:2289
worker_thread+0x340/0x610 kernel/workqueue.c:2436
kthread+0x12c/0x158 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:863
Code: 14000002 97d01d05 f9403335 2a1f03e0 (b94002ba)
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
0: 14000002 b 0x8
4: 97d01d05 bl 0xffffffffff407418
8: f9403335 ldr x21, [x25, #96]
c: 2a1f03e0 mov w0, wzr
* 10: b94002ba ldr w26, [x21] <-- 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.

[syzbot]

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