[syzbot] [jfs?] WARNING in dbJoin

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: b1cbabe84ca1 Merge tag 'for-7.2/dm-changes' of git://git.k..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1483a3b6580000
kernel config: https://syzkaller.appspot.com/x/.config?x=effd10de8797244
dashboard link: https://syzkaller.appspot.com/bug?extid=a67911c5a11315aa55a8
compiler: Debian clang version 22.1.6 (++20260514074242+fc4aad7b5db3-1~exp1~20260514074407.73), Debian LLD 22.1.6

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/965fde89d8ba/disk-b1cbabe8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6e68a7e15b8d/vmlinux-b1cbabe8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6ffa4967bc81/bzImage-b1cbabe8.xz

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

------------[ cut here ]------------
lp >= size || lp < 0
WARNING: fs/jfs/jfs_dmap.c:2962 at dbAdjTree fs/jfs/jfs_dmap.c:2962 [inline], CPU#1: jfsCommit/128
WARNING: fs/jfs/jfs_dmap.c:2962 at dbJoin+0xc33/0xd60 fs/jfs/jfs_dmap.c:2930, CPU#1: jfsCommit/128
Modules linked in:
CPU: 1 UID: 0 PID: 128 Comm: jfsCommit Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/09/2026
RIP: 0010:dbAdjTree fs/jfs/jfs_dmap.c:2962 [inline]
RIP: 0010:dbJoin+0xc33/0xd60 fs/jfs/jfs_dmap.c:2930
Code: eb 0c e8 a0 ca 6e fe eb 05 e8 99 ca 6e fe 31 c0 48 83 c4 68 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc cc e8 7e ca 6e fe 90 <0f> 0b 90 eb df 44 89 e9 80 e1 07 38 c1 0f 8c 00 f4 ff ff 4c 89 ef
RSP: 0000:ffffc9000156fa28 EFLAGS: 00010293
RAX: ffffffff8355f172 RBX: 0000000000000155 RCX: ffff88801eb75d00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000004 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: fffff940002ddfb9 R12: dffffc0000000000
R13: ffff88805bbf7020 R14: 0000000000020056 R15: 0000000000000004
FS: 0000000000000000(0000) GS:ffff88812647d000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f39082e6000 CR3: 00000000600f2000 CR4: 00000000003526f0
Call Trace:
<TASK>
dbFreeBits+0x4a2/0xd70 fs/jfs/jfs_dmap.c:2427
dbFreeDmap fs/jfs/jfs_dmap.c:2176 [inline]
dbFree+0x324/0x650 fs/jfs/jfs_dmap.c:485
txFreeMap+0x7ff/0xde0 fs/jfs/jfs_txnmgr.c:2536
txUpdateMap+0x32d/0x9f0 fs/jfs/jfs_txnmgr.c:-1
txLazyCommit fs/jfs/jfs_txnmgr.c:2666 [inline]
jfs_lazycommit+0x3f3/0xa20 fs/jfs/jfs_txnmgr.c:2735
kthread+0x388/0x470 kernel/kthread.c:436
ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</TASK>


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