Hello,
syzbot found the following issue on:
HEAD commit: c2603c511feb Linux 6.6.93
git tree: linux-6.6.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=1415790c580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=486bade17c8c30b9
dashboard link:
https://syzkaller.appspot.com/bug?extid=a69dfcbd991f4b75fc50
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/8754f950a6e7/disk-c2603c51.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/3b19332dbf63/vmlinux-c2603c51.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/cb245e836038/bzImage-c2603c51.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+a69dfc...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 111 at fs/jfs/jfs_dmap.c:2882 dbAdjTree+0x448/0x4d0 fs/jfs/jfs_dmap.c:2882
Modules linked in:
CPU: 0 PID: 111 Comm: jfsCommit Not tainted 6.6.93-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:dbAdjTree+0x448/0x4d0 fs/jfs/jfs_dmap.c:2882
Code: e8 6d 32 e0 fe e9 5a ff ff ff e8 d3 8d 87 fe eb 05 e8 cc 8d 87 fe 48 83 c4 28 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 b8 8d 87 fe <0f> 0b eb e8 44 89 e1 80 e1 07 80 c1 03 38 c1 0f 8c ee fb ff ff 4c
RSP: 0018:ffffc90002647ac8 EFLAGS: 00010293
RAX: ffffffff82fe0928 RBX: ffff888068b37010 RCX: ffff88801a301e00
RDX: 0000000000000000 RSI: 0000000000000155 RDI: 0000000000020056
RBP: 0000000000020056 R08: ffffea0001a2cdc7 R09: 1ffffd40003459b8
R10: dffffc0000000000 R11: fffff940003459b9 R12: ffff888068b37018
R13: dffffc0000000000 R14: 0000000000000004 R15: 0000000000000155
FS: 0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055557b1f25c8 CR3: 000000002f41e000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
dbJoin+0x238/0x300 fs/jfs/jfs_dmap.c:2850
dbFreeBits+0x4e2/0xdb0 fs/jfs/jfs_dmap.c:2347
dbFreeDmap fs/jfs/jfs_dmap.c:2096 [inline]
dbFree+0x332/0x650 fs/jfs/jfs_dmap.c:413
txFreeMap+0x7ff/0xde0 fs/jfs/jfs_txnmgr.c:2534
txUpdateMap+0x306/0x890 fs/jfs/jfs_txnmgr.c:-1
txLazyCommit fs/jfs/jfs_txnmgr.c:2664 [inline]
jfs_lazycommit+0x42b/0xa60 fs/jfs/jfs_txnmgr.c:2732
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</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