Hello,
syzbot found the following issue on:
HEAD commit: fdb6fcb41cc7 Linux 6.1.176
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=1267bdee580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=f312e19619d04f50
dashboard link:
https://syzkaller.appspot.com/bug?extid=5a9c5fc22f22f9be4f30
compiler: Debian clang version 22.1.6 (++20260514074242+fc4aad7b5db3-1~exp1~20260514074407.73), Debian LLD 22.1.6
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/be13f594160c/disk-fdb6fcb4.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/861f249f1e1c/vmlinux-fdb6fcb4.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/59bb274672f8/Image-fdb6fcb4.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+5a9c5f...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 93 at fs/jfs/jfs_dmap.c:2875 dbAdjTree fs/jfs/jfs_dmap.c:-1 [inline]
WARNING: CPU: 1 PID: 93 at fs/jfs/jfs_dmap.c:2875 dbJoin+0xa08/0xb0c fs/jfs/jfs_dmap.c:2843
Modules linked in:
CPU: 1 PID: 93 Comm: jfsCommit Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/02/2026
pstate: 82400005 (Nzcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=--)
pc : dbAdjTree fs/jfs/jfs_dmap.c:-1 [inline]
pc : dbJoin+0xa08/0xb0c fs/jfs/jfs_dmap.c:2843
lr : dbAdjTree fs/jfs/jfs_dmap.c:2875 [inline]
lr : dbJoin+0xa04/0xb0c fs/jfs/jfs_dmap.c:2843
sp : ffff80001ff67480
x29: ffff80001ff674e0 x28: 0000000000000000 x27: ffff0000e8b16010
x26: ffff0000e8b16804 x25: 0000000000000001 x24: 0000000000000001
x23: 1fffe0001d162c04 x22: 0000000000000155 x21: 0000000000020056
x20: 0000000000000004 x19: dfff800000000000 x18: 1fffe00033e8417e
x17: ffff8000098e0f0c x16: ffff8000082dba2c x15: 0000000000000000
x14: 0000000000000001 x13: 1fffff80007458b0 x12: 0000000000000000
x11: ff008000098c3e98 x10: 0000000000000000 x9 : ffff8000098c3e98
x8 : ffff0000c78b9c00 x7 : ffff8000086fd3fc x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000
x2 : 0000000000000004 x1 : 0000000000000155 x0 : 0000000000000000
Call trace:
dbAdjTree fs/jfs/jfs_dmap.c:-1 [inline]
dbJoin+0xa08/0xb0c fs/jfs/jfs_dmap.c:2843
dbFreeBits+0x40c/0xbf4 fs/jfs/jfs_dmap.c:2340
dbFreeDmap fs/jfs/jfs_dmap.c:2089 [inline]
dbFree+0x2dc/0x5d4 fs/jfs/jfs_dmap.c:398
txFreeMap+0x800/0xb94 fs/jfs/jfs_txnmgr.c:2516
xtTruncate+0xa1c/0x266c fs/jfs/jfs_xtree.c:2467
jfs_free_zero_link+0x2c0/0x424 fs/jfs/namei.c:758
jfs_evict_inode+0x2f4/0x3e4 fs/jfs/inode.c:159
evict+0x3d8/0x824 fs/inode.c:705
iput_final fs/inode.c:1834 [inline]
iput+0x728/0x7e8 fs/inode.c:1860
txUpdateMap+0x68c/0x7b0 fs/jfs/jfs_txnmgr.c:2368
txLazyCommit fs/jfs/jfs_txnmgr.c:2665 [inline]
jfs_lazycommit+0x360/0x930 fs/jfs/jfs_txnmgr.c:2733
kthread+0x254/0x2e0 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:850
irq event stamp: 70
hardirqs last enabled at (69): [<ffff800011c25a1c>] __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:151 [inline]
hardirqs last enabled at (69): [<ffff800011c25a1c>] _raw_spin_unlock_irqrestore+0x48/0xac kernel/locking/spinlock.c:194
hardirqs last disabled at (70): [<ffff800011b3a55c>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (0): [<ffff80000818be70>] copy_process+0x1370/0x38f4 kernel/fork.c:2302
softirqs last disabled at (0): [<0000000000000000>] 0x0
---[ end trace 0000000000000000 ]---
---
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