[v5.15] kernel BUG in __ocfs2_move_extents_range (2)

0 views
Skip to first unread message

syzbot

unread,
Dec 31, 2025, 8:22:23 PM (7 days ago) 12/31/25
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 68efe5a6c16a Linux 5.15.197
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14f8529a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7e6ed99963d6ee1d
dashboard link: https://syzkaller.appspot.com/bug?extid=4af7de062c539ffd4451
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/900f9b9bd850/disk-68efe5a6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1e089a5019a6/vmlinux-68efe5a6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b319f477b907/bzImage-68efe5a6.xz

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

------------[ cut here ]------------
kernel BUG at fs/ocfs2/suballoc.c:1349!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 4441 Comm: syz.3.29 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:ocfs2_block_group_set_bits+0x531/0x650 fs/ocfs2/suballoc.c:1349
Code: ff 44 89 f9 80 e1 07 fe c1 38 c1 0f 8c 85 fd ff ff 4c 89 ff e8 20 69 9a fe e9 78 fd ff ff e8 96 00 56 fe 0f 0b e8 8f 00 56 fe <0f> 0b 65 44 8b 3d cd 49 e0 7c bf 07 00 00 00 44 89 fe e8 d8 03 56
RSP: 0018:ffffc900033ef3a0 EFLAGS: 00010246
RAX: ffffffff8321cb81 RBX: 000000000000003f RCX: 0000000000080000
RDX: ffffc9000ef1c000 RSI: 000000000007ffff RDI: 0000000000080000
RBP: ffffc900033ef490 R08: 00000000000003c5 R09: 000000000000003f
R10: 00000000fffffffc R11: 0000000000000002 R12: dffffc0000000000
R13: 00000000000003c5 R14: ffff88806432d000 R15: 000000000000003a
FS: 00007f39e80b96c0(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000001000 CR3: 000000005fb4c000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ocfs2_move_extent fs/ocfs2/move_extents.c:687 [inline]
__ocfs2_move_extents_range+0x2978/0x3370 fs/ocfs2/move_extents.c:860
ocfs2_move_extents+0x37c/0x960 fs/ocfs2/move_extents.c:932
ocfs2_ioctl_move_extents+0x4dd/0x6b0 fs/ocfs2/move_extents.c:1058
ocfs2_ioctl+0x2d9/0x720 fs/ocfs2/ioctl.c:931
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:874 [inline]
__se_sys_ioctl+0xfa/0x170 fs/ioctl.c:860
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f39e9e73749
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:00007f39e80b9038 EFLAGS: 00000246
ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f39ea0ca090 RCX: 00007f39e9e73749
RDX: 00002000000000c0 RSI: 0000000040406f06 RDI: 0000000000000005
RBP: 00007f39e9ef7f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f39ea0ca128 R14: 00007f39ea0ca090 R15: 00007ffc553c1148
</TASK>
Modules linked in:
---[ end trace c5ed6371439185bb ]---
RIP: 0010:ocfs2_block_group_set_bits+0x531/0x650 fs/ocfs2/suballoc.c:1349
Code: ff 44 89 f9 80 e1 07 fe c1 38 c1 0f 8c 85 fd ff ff 4c 89 ff e8 20 69 9a fe e9 78 fd ff ff e8 96 00 56 fe 0f 0b e8 8f 00 56 fe <0f> 0b 65 44 8b 3d cd 49 e0 7c bf 07 00 00 00 44 89 fe e8 d8 03 56
RSP: 0018:ffffc900033ef3a0 EFLAGS: 00010246

RAX: ffffffff8321cb81 RBX: 000000000000003f RCX: 0000000000080000
RDX: ffffc9000ef1c000 RSI: 000000000007ffff RDI: 0000000000080000
RBP: ffffc900033ef490 R08: 00000000000003c5 R09: 000000000000003f
R10: 00000000fffffffc R11: 0000000000000002 R12: dffffc0000000000
R13: 00000000000003c5 R14: ffff88806432d000 R15: 000000000000003a
FS: 00007f39e80b96c0(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffd95e7abd8 CR3: 000000005fb4c000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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
Reply all
Reply to author
Forward
0 new messages