[v6.1] BUG: unable to handle kernel paging request in dbUpdatePMap

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: f6e38ae624cf Linux 6.1.158
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13e1d97c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=68aa5a3af1cb953a
dashboard link: https://syzkaller.appspot.com/bug?extid=8b9738aed3fee77451a0
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13eb5a12580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c1bd671a9def/disk-f6e38ae6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fa0af998ea40/vmlinux-f6e38ae6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e5512d873524/Image-f6e38ae6.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/0ad08da4e9d8/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=1529b742580000)

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

Unable to handle kernel paging request at virtual address fbd5200000000021
KASAN: maybe wild-memory-access in range [0xdead000000000108-0xdead00000000010f]
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
[fbd5200000000021] address between user and kernel address ranges
Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 92 Comm: jfsCommit Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/03/2025
pstate: 824000c5 (Nzcv daIF +PAN -UAO +TCO -DIT -SSBS BTYPE=--)
pc : __list_add_valid+0x3c/0x110 lib/list_debug.c:27
lr : __list_add include/linux/list.h:69 [inline]
lr : list_add include/linux/list.h:88 [inline]
lr : dbUpdatePMap+0x5f0/0xc40 fs/jfs/jfs_dmap.c:577
sp : ffff80001cf47ac0
x29: ffff80001cf47ac0 x28: 0000000000000004 x27: ffff0000caf8b2e8
x26: dfff800000000000 x25: 0000000000000004 x24: dead000000000100
x23: dfff800000000000 x22: dead000000000108 x21: ffff0000caf8b2f8
x20: ffff80001fd19340 x19: dead000000000100 x18: ffff800011abbcc0
x17: 1fffe00033ed797e x16: ffff8000082e7914 x15: ffff8000150bd000
x14: 0000000000000100 x13: 1ffff00002a180b1 x12: 0000000000ff0100
x11: ff0080000986e11c x10: ffff0000d4ec9280 x9 : 0000000000000000
x8 : 1bd5a00000000021 x7 : ffff80000986e0e8 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : ffff8000082e7a34
x2 : dead000000000100 x1 : ffff80001fd19340 x0 : ffff0000caf8b2f8
Call trace:
__list_add_valid+0x3c/0x110 lib/list_debug.c:27
__list_add include/linux/list.h:69 [inline]
list_add include/linux/list.h:88 [inline]
dbUpdatePMap+0x5f0/0xc40 fs/jfs/jfs_dmap.c:577
txAllocPMap+0x4a0/0x5d4 fs/jfs/jfs_txnmgr.c:2425
txUpdateMap+0x628/0x79c fs/jfs/jfs_txnmgr.c:2363
txLazyCommit fs/jfs/jfs_txnmgr.c:2664 [inline]
jfs_lazycommit+0x378/0x918 fs/jfs/jfs_txnmgr.c:2732
kthread+0x250/0x2d8 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:850
Code: aa0103f4 d343fec8 f2fbfff7 aa0003f5 (38776908)
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
0: aa0103f4 mov x20, x1
4: d343fec8 lsr x8, x22, #3
8: f2fbfff7 movk x23, #0xdfff, lsl #48
c: aa0003f5 mov x21, x0
* 10: 38776908 ldrb w8, [x8, x23] <-- 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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

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]

syzbot has found a reproducer for the following issue on:

HEAD commit: f6e38ae624cf Linux 6.1.158
git tree: linux-6.1.y

console output: https://syzkaller.appspot.com/x/log.txt?x=12e298b4580000

kernel config: https://syzkaller.appspot.com/x/.config?x=68aa5a3af1cb953a
dashboard link: https://syzkaller.appspot.com/bug?extid=8b9738aed3fee77451a0
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
userspace arch: arm64

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1355fa12580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=144dc484580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c1bd671a9def/disk-f6e38ae6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fa0af998ea40/vmlinux-f6e38ae6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e5512d873524/Image-f6e38ae6.gz.xz

mounted in repro: https://storage.googleapis.com/syzbot-assets/f5f2a61890a6/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=14d5b742580000)

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

Unable to handle kernel paging request at virtual address fbd5200000000021
KASAN: maybe wild-memory-access in range [0xdead000000000108-0xdead00000000010f]
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
[fbd5200000000021] address between user and kernel address ranges
Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP
Modules linked in:

CPU: 1 PID: 92 Comm: jfsCommit Not tainted syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/03/2025
pstate: 824000c5 (Nzcv daIF +PAN -UAO +TCO -DIT -SSBS BTYPE=--)
pc : __list_add_valid+0x3c/0x110 lib/list_debug.c:27
lr : __list_add include/linux/list.h:69 [inline]
lr : list_add include/linux/list.h:88 [inline]
lr : dbUpdatePMap+0x5f0/0xc40 fs/jfs/jfs_dmap.c:577

sp : ffff80001ce97ac0
x29: ffff80001ce97ac0 x28: 0000000000000004 x27: ffff0000c983a1f0

x26: dfff800000000000 x25: 0000000000000004 x24: dead000000000100

x23: dfff800000000000 x22: dead000000000108 x21: ffff0000c983a200
x20: ffff80001fd29120 x19: dead000000000100 x18: ffff800011abbcc0
x17: 1fffe00033edbb7e x16: ffff8000082e7914 x15: ffff8000150bd000

x14: 0000000000000100 x13: 1ffff00002a180b1 x12: 0000000000ff0100

x11: ff0080000986e11c x10: ffff0000d5053a80 x9 : 0000000000000000

x8 : 1bd5a00000000021 x7 : ffff80000986e0e8 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : ffff8000082e7a34

x2 : dead000000000100 x1 : ffff80001fd29120 x0 : ffff0000c983a200

Call trace:
__list_add_valid+0x3c/0x110 lib/list_debug.c:27
__list_add include/linux/list.h:69 [inline]
list_add include/linux/list.h:88 [inline]
dbUpdatePMap+0x5f0/0xc40 fs/jfs/jfs_dmap.c:577
txAllocPMap+0x4a0/0x5d4 fs/jfs/jfs_txnmgr.c:2425
txUpdateMap+0x628/0x79c fs/jfs/jfs_txnmgr.c:2363
txLazyCommit fs/jfs/jfs_txnmgr.c:2664 [inline]
jfs_lazycommit+0x378/0x918 fs/jfs/jfs_txnmgr.c:2732
kthread+0x250/0x2d8 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:850
Code: aa0103f4 d343fec8 f2fbfff7 aa0003f5 (38776908)
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
0: aa0103f4 mov x20, x1
4: d343fec8 lsr x8, x22, #3
8: f2fbfff7 movk x23, #0xdfff, lsl #48
c: aa0003f5 mov x21, x0
* 10: 38776908 ldrb w8, [x8, x23] <-- trapping instruction


---