Hello,
syzbot found the following issue on:
HEAD commit: 355bd0b51d2f Linux 6.6.104
git tree: linux-6.6.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=15e5f562580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=dac93b93d3de2741
dashboard link:
https://syzkaller.appspot.com/bug?extid=4bf1a50375cfc097f79d
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/ef00d28b2c5b/disk-355bd0b5.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/7627cd51eb0a/vmlinux-355bd0b5.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/3fdd0a51dd65/bzImage-355bd0b5.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+4bf1a5...@syzkaller.appspotmail.com
ocfs2: Mounting device (7,1) on (node local, slot 0) with ordered data mode.
------------[ cut here ]------------
kernel BUG at fs/ocfs2/suballoc.c:1349!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 8713 Comm: syz.1.684 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
RIP: 0010:ocfs2_block_group_set_bits+0x53e/0x670 fs/ocfs2/suballoc.c:1349
Code: ff 44 89 f9 80 e1 07 fe c1 38 c1 0f 8c 8e fd ff ff 4c 89 ff e8 63 27 83 fe e9 81 fd ff ff e8 49 e1 2b fe 0f 0b e8 42 e1 2b fe <0f> 0b f3 0f 1e fa 65 44 8b 3d a0 0b aa 7c bf 07 00 00 00 44 89 fe
RSP: 0000:ffffc9000c336840 EFLAGS: 00010283
RAX: ffffffff8359ae5e RBX: 0000000000000040 RCX: 0000000000080000
RDX: ffffc9000b9e9000 RSI: 000000000001fa9d RDI: 000000000001fa9e
RBP: ffffc9000c336930 R08: 0000000000000255 R09: 0000000000000040
R10: 00000000fffffffc R11: 0000000000000002 R12: dffffc0000000000
R13: 0000000000000255 R14: ffff88802e9c3000 R15: 0000000000000003
FS: 00007fc5371246c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f40bd3ad000 CR3: 000000002b39d000 CR4: 00000000003506f0
Call Trace:
<TASK>
ocfs2_search_chain+0x1986/0x22c0 fs/ocfs2/suballoc.c:1847
ocfs2_claim_suballoc_bits+0xfdf/0x2230 fs/ocfs2/suballoc.c:1930
__ocfs2_claim_clusters+0x302/0x900 fs/ocfs2/suballoc.c:2338
ocfs2_claim_clusters fs/ocfs2/suballoc.c:2375 [inline]
ocfs2_block_group_alloc_contig fs/ocfs2/suballoc.c:428 [inline]
ocfs2_block_group_alloc fs/ocfs2/suballoc.c:695 [inline]
ocfs2_reserve_suballoc_bits+0xe7e/0x4360 fs/ocfs2/suballoc.c:828
ocfs2_reserve_new_metadata_blocks+0x404/0x940 fs/ocfs2/suballoc.c:978
ocfs2_reserve_new_metadata fs/ocfs2/suballoc.c:1021 [inline]
ocfs2_lock_allocators+0x29f/0x5b0 fs/ocfs2/suballoc.c:2658
ocfs2_extend_allocation+0x39b/0x1760 fs/ocfs2/file.c:589
ocfs2_allocate_unwritten_extents+0x2ea/0x7b0 fs/ocfs2/file.c:1495
__ocfs2_change_file_space+0x8d6/0xe40 fs/ocfs2/file.c:2022
ocfs2_fallocate+0x1f5/0x240 fs/ocfs2/file.c:2137
vfs_fallocate+0x58e/0x700 fs/open.c:324
ksys_fallocate fs/open.c:347 [inline]
__do_sys_fallocate fs/open.c:355 [inline]
__se_sys_fallocate fs/open.c:353 [inline]
__x64_sys_fallocate+0xc1/0x110 fs/open.c:353
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fc53638ebe9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fc537124038 EFLAGS: 00000246 ORIG_RAX: 000000000000011d
RAX: ffffffffffffffda RBX: 00007fc5365c5fa0 RCX: 00007fc53638ebe9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000004
RBP: 00007fc536411e19 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000008000c62 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fc5365c6038 R14: 00007fc5365c5fa0 R15: 00007fff1163e4f8
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:ocfs2_block_group_set_bits+0x53e/0x670 fs/ocfs2/suballoc.c:1349
Code: ff 44 89 f9 80 e1 07 fe c1 38 c1 0f 8c 8e fd ff ff 4c 89 ff e8 63 27 83 fe e9 81 fd ff ff e8 49 e1 2b fe 0f 0b e8 42 e1 2b fe <0f> 0b f3 0f 1e fa 65 44 8b 3d a0 0b aa 7c bf 07 00 00 00 44 89 fe
RSP: 0000:ffffc9000c336840 EFLAGS: 00010283
RAX: ffffffff8359ae5e RBX: 0000000000000040 RCX: 0000000000080000
RDX: ffffc9000b9e9000 RSI: 000000000001fa9d RDI: 000000000001fa9e
RBP: ffffc9000c336930 R08: 0000000000000255 R09: 0000000000000040
R10: 00000000fffffffc R11: 0000000000000002 R12: dffffc0000000000
R13: 0000000000000255 R14: ffff88802e9c3000 R15: 0000000000000003
FS: 00007fc5371246c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f88f6d93ad8 CR3: 000000002b39d000 CR4: 00000000003506e0
---
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