linux-kernel - [syzbot] [xfs?] BUG: unable to handle kernel paging request in xlog_cil_push

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <68127bff.050a0220.3a872c.0007.GAE@google.com>
Date: Wed, 30 Apr 2025 12:37:35 -0700
From: syzbot <syzbot+8f3eae9a167883ac95d5@...kaller.appspotmail.com>
To: cem@...nel.org, djwong@...nel.org, linux-kernel@...r.kernel.org, 
	linux-xfs@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: [syzbot] [xfs?] BUG: unable to handle kernel paging request in xlog_cil_push_work

Hello,

syzbot found the following issue on:

HEAD commit:    b5737d35364f 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=13376e98580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=12ccc0a681e19f95
dashboard link: https://syzkaller.appspot.com/bug?extid=8f3eae9a167883ac95d5
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/02e0fdf59f95/disk-b5737d35.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9f13fee8534d/vmlinux-b5737d35.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e3a18c045780/Image-b5737d35.gz.xz

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

Unable to handle kernel paging request at virtual address 001f7fe0001abb51
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
[001f7fe0001abb51] address between user and kernel address ranges
Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 UID: 0 PID: 12 Comm: kworker/u8:0 Not tainted 6.14.0-rc7-syzkaller-gb5737d35364f #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Workqueue: xfs-cil/loop1 xlog_cil_push_work
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : xlog_cil_build_lv_chain fs/xfs/xfs_log_cil.c:1245 [inline]
pc : xlog_cil_push_work+0xb68/0x25d4 fs/xfs/xfs_log_cil.c:1381
lr : generic_test_bit include/asm-generic/bitops/generic-non-atomic.h:128 [inline]
lr : xlog_cil_build_lv_chain fs/xfs/xfs_log_cil.c:1238 [inline]
lr : xlog_cil_push_work+0xb1c/0x25d4 fs/xfs/xfs_log_cil.c:1381
sp : ffff800097d476e0
x29: ffff800097d47a20 x28: ffff0000db7b5c19 x27: 00ffff0000d5da7c
x26: ffff0000ce2940b0 x25: ffff800097d479d0 x24: dfff800000000000
x23: ffff0000db7b5bf1 x22: 1fffe0001b6f6b83 x21: ffff0000db7b5c01
x20: ffff0000db7b5bc9 x19: dfff800000000000 x18: 0000000000004000
x17: ffff80008fbbd000 x16: ffff8000803b975c x15: 0000000000000001
x14: 1fffe0001a69c720 x13: 0000000000000000 x12: 0000000000000000
x11: 0000000000000001 x10: 0000000000ff0100 x9 : 0000000000000000
x8 : 001fffe0001abb51 x7 : ffff800081f89378 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff800080482fd8
x2 : 0000000000000001 x1 : 0000000000000000 x0 : 00ffff0000d5da8c
Call trace:
 xlog_cil_build_lv_chain fs/xfs/xfs_log_cil.c:1245 [inline] (P)
 xlog_cil_push_work+0xb68/0x25d4 fs/xfs/xfs_log_cil.c:1381 (P)
 process_one_work+0x810/0x1638 kernel/workqueue.c:3238
 process_scheduled_works kernel/workqueue.c:3319 [inline]
 worker_thread+0x97c/0xeec kernel/workqueue.c:3400
 kthread+0x65c/0x7b0 kernel/kthread.c:464
 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:862
Code: 91004360 d2d00013 d343fc08 f2fbfff3 (38f86908) 
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
   0:	91004360 	add	x0, x27, #0x10
   4:	d2d00013 	mov	x19, #0x800000000000        	// #140737488355328
   8:	d343fc08 	lsr	x8, x0, #3
   c:	f2fbfff3 	movk	x19, #0xdfff, lsl #48
* 10:	38f86908 	ldrsb	w8, [x8, x24] <-- 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 syzkaller@...glegroups.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