[v5.15] kernel BUG in dbFindLeaf

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d54cfc420586 Linux 5.15.120
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11d2985aa80000
kernel config: https://syzkaller.appspot.com/x/.config?x=61785ceccc6bdf75
dashboard link: https://syzkaller.appspot.com/bug?extid=f0b9c8f03467ee4e5852
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/df6c88d1a764/disk-d54cfc42.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/787a9f4e718c/vmlinux-d54cfc42.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4a60832537ff/Image-d54cfc42.gz.xz

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

loop2: detected capacity change from 0 to 32768
BUG at fs/jfs/jfs_dmap.c:3017 assert(n < 4)
------------[ cut here ]------------
kernel BUG at fs/jfs/jfs_dmap.c:3017!
Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 15058 Comm: syz-executor.2 Not tainted 5.15.120-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : dbFindLeaf+0x3e0/0x3e4 fs/jfs/jfs_dmap.c:3017
lr : dbFindLeaf+0x3e0/0x3e4 fs/jfs/jfs_dmap.c:3017
sp : ffff80001e6d6e70
x29: ffff80001e6d6e80 x28: 0000000000000012 x27: dfff800000000000
x26: 00000000ffffffff x25: 0000000000000014 x24: ffff800014e3fb10
x23: 0000000000000011 x22: 0000000000000003 x21: 0000000000000000
x20: ffff0000c791a010 x19: ffff80001e6d6f20 x18: 0000000000000001
x17: ff80800008335ea8 x16: ffff80001195b9f4 x15: ffff800008335ea8
x14: 00000000ffffffff x13: ffffffffffffffff x12: 0000000000040000
x11: 000000000003ffff x10: ffff80001fdca000 x9 : 8d77c9f640579500
x8 : 8d77c9f640579500 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff80001e6d65d8 x4 : ffff8000149cfca0 x3 : ffff80000a954f60
x2 : ffff0001b4819d10 x1 : 0000000100000000 x0 : 000000000000002b
Call trace:
dbFindLeaf+0x3e0/0x3e4 fs/jfs/jfs_dmap.c:3017
dbAllocDmapLev+0xc4/0x3b8 fs/jfs/jfs_dmap.c:2021
dbAllocCtl+0x104/0x874 fs/jfs/jfs_dmap.c:1877
dbAllocAG+0x208/0xe4c fs/jfs/jfs_dmap.c:1418
dbAlloc+0x4b0/0xa18 fs/jfs/jfs_dmap.c:874
extBalloc fs/jfs/jfs_extent.c:518 [inline]
extAlloc+0x3f0/0xe38 fs/jfs/jfs_extent.c:125
jfs_get_block+0x34c/0xbfc fs/jfs/inode.c:258
nobh_write_begin+0x2d8/0xa28 fs/buffer.c:2650
jfs_write_begin+0x58/0xa0 fs/jfs/inode.c:322
generic_perform_write+0x24c/0x520 mm/filemap.c:3776
__generic_file_write_iter+0x230/0x454 mm/filemap.c:3903
generic_file_write_iter+0xb4/0x1b8 mm/filemap.c:3935
do_iter_readv_writev+0x420/0x5f8
do_iter_write+0x1b8/0x664 fs/read_write.c:855
vfs_writev fs/read_write.c:928 [inline]
do_pwritev+0x1ec/0x334 fs/read_write.c:1025
__do_sys_pwritev2 fs/read_write.c:1084 [inline]
__se_sys_pwritev2 fs/read_write.c:1075 [inline]
__arm64_sys_pwritev2+0xd4/0x108 fs/read_write.c:1075
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: d0042a03 91028063 52817922 959a070d (d4210000)
---[ end trace 4af28d0347c3c12d ]---


---
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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, 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: d54cfc420586 Linux 5.15.120
git tree: linux-5.15.y

console output: https://syzkaller.appspot.com/x/log.txt?x=10b6205ca80000

kernel config: https://syzkaller.appspot.com/x/.config?x=61785ceccc6bdf75
dashboard link: https://syzkaller.appspot.com/bug?extid=f0b9c8f03467ee4e5852
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1294e7e2a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12363ef8a80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/df6c88d1a764/disk-d54cfc42.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/787a9f4e718c/vmlinux-d54cfc42.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4a60832537ff/Image-d54cfc42.gz.xz

mounted in repro: https://storage.googleapis.com/syzbot-assets/8f67297faf27/mount_0.gz

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

loop0: detected capacity change from 0 to 32768

BUG at fs/jfs/jfs_dmap.c:3017 assert(n < 4)
------------[ cut here ]------------
kernel BUG at fs/jfs/jfs_dmap.c:3017!
Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
Modules linked in:

CPU: 1 PID: 3962 Comm: syz-executor150 Not tainted 5.15.120-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : dbFindLeaf+0x3e0/0x3e4 fs/jfs/jfs_dmap.c:3017
lr : dbFindLeaf+0x3e0/0x3e4 fs/jfs/jfs_dmap.c:3017

sp : ffff80001cb26e70
x29: ffff80001cb26e80 x28: 0000000000000012 x27: dfff800000000000

x26: 00000000ffffffff x25: 0000000000000014 x24: ffff800014e3fb10
x23: 0000000000000011 x22: 0000000000000003 x21: 0000000000000000

x20: ffff0000c8206010 x19: ffff80001cb26f20 x18: 0000000000000001

x17: ff80800008335ea8 x16: ffff80001195b9f4 x15: ffff800008335ea8

x14: 00000000ffffffff x13: ffffffffffffffff x12: 0000000000000000
x11: ff8080000832d950 x10: 0000000000000000 x9 : 3ec33fb7c7934e00
x8 : 3ec33fb7c7934e00 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff80001cb265d8 x4 : ffff8000149cfca0 x3 : ffff80000a954f60

---[ end trace 7ed5753015a37576 ]---


---
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.