All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+7960178e777909060224@syzkaller.appspotmail.com>
To: jlbec@evilplan.org, joseph.qi@linux.alibaba.com,
	 linux-kernel@vger.kernel.org, mark@fasheh.com,
	ocfs2-devel@lists.linux.dev,  syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] kernel BUG in ocfs2_move_extents
Date: Tue, 23 Dec 2025 12:31:20 -0800	[thread overview]
Message-ID: <694afc18.050a0220.35954c.0006.GAE@google.com> (raw)
In-Reply-To: <69441a92.a70a0220.207337.00e4.GAE@google.com>

syzbot has found a reproducer for the following issue on:

HEAD commit:    8f0b4cce4481 Linux 6.19-rc1
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=12eb8bb4580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=8a8594efdc14f07a
dashboard link: https://syzkaller.appspot.com/bug?extid=7960178e777909060224
compiler:       Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
userspace arch: arm64
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=14838f1a580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=16eb8bb4580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/cd4f5f43efc8/disk-8f0b4cce.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/aafb35ac3a3c/vmlinux-8f0b4cce.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d221fae4ab17/Image-8f0b4cce.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/2c226c2e3d21/mount_0.gz
  fsck result: OK (log: https://syzkaller.appspot.com/x/fsck.log?x=10838f1a580000)

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

=======================================================
JBD2: Ignoring recovery information on journal
ocfs2: Mounting device (7,0) on (node local, slot 0) with ordered data mode.
------------[ cut here ]------------
kernel BUG at fs/ocfs2/suballoc.c:1383!
Internal error: Oops - BUG: 00000000f2000800 [#1]  SMP
Modules linked in:
CPU: 1 UID: 0 PID: 6734 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/03/2025
pstate: 83400005 (Nzcv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)
pc : ocfs2_block_group_set_bits+0x784/0x8ec fs/ocfs2/suballoc.c:1383
lr : ocfs2_block_group_set_bits+0x784/0x8ec fs/ocfs2/suballoc.c:1383
sp : ffff8000a3eb7260
x29: ffff8000a3eb7320 x28: ffff0000f60124f8 x27: ffff0000ca05c000
x26: ffff0000eaee1b00 x25: ffff0000c5c8c000 x24: 1ffff000147d6e58
x23: ffff0000c5c8c00c x22: dfff800000000000 x21: 0000000000000001
x20: 0000000000000002 x19: 0000000000000000 x18: 00000000ffffffff
x17: ffff800082225fb0 x16: ffff80008af67980 x15: 0000000000000001
x14: 0000000000000000 x13: 00000000fffffffc x12: 0000000000000000
x11: 0000000000000000 x10: 0000000000ff0100 x9 : 0000000000000000
x8 : ffff0000c8f1d580 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000002 x4 : 0000000000000001 x3 : ffff0000c1707d98
x2 : ffff0000c5c8c000 x1 : 0000000000000001 x0 : 0000000000000002
Call trace:
 ocfs2_block_group_set_bits+0x784/0x8ec fs/ocfs2/suballoc.c:1383 (P)
 ocfs2_move_extent fs/ocfs2/move_extents.c:693 [inline]
 __ocfs2_move_extents_range fs/ocfs2/move_extents.c:865 [inline]
 ocfs2_move_extents+0x213c/0x2e78 fs/ocfs2/move_extents.c:937
 ocfs2_ioctl_move_extents+0x448/0x614 fs/ocfs2/move_extents.c:1069
 ocfs2_ioctl+0x1c4/0x738 fs/ocfs2/ioctl.c:942
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:597 [inline]
 __se_sys_ioctl fs/ioctl.c:583 [inline]
 __arm64_sys_ioctl+0x14c/0x1c4 fs/ioctl.c:583
 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
 invoke_syscall+0x98/0x254 arch/arm64/kernel/syscall.c:49
 el0_svc_common+0xe8/0x23c arch/arm64/kernel/syscall.c:132
 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151
 el0_svc+0x5c/0x26c arch/arm64/kernel/entry-common.c:724
 el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:743
 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:596
Code: 17ffffa0 97944b2d d4210000 97944b2b (d4210000) 
---[ end trace 0000000000000000 ]---


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

  reply	other threads:[~2025-12-23 20:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-18 15:15 [syzbot] [ocfs2?] kernel BUG in ocfs2_move_extents syzbot
2025-12-23 20:31 ` syzbot [this message]
2025-12-31  5:05 ` Forwarded: [PATCH] ocfs2: add debug printk to trace block group validation path syzbot
2025-12-31  7:51 ` Forwarded: [PATCH] ocfs2: add check for free bits before allocation in ocfs2_move_extent() syzbot
2025-12-31  7:52 ` syzbot
2026-01-04 11:49 ` syzbot
2026-01-04 12:26 ` syzbot
     [not found] <20251231050537.50481-1-kartikey406@gmail.com>
2025-12-31  5:35 ` [syzbot] [ocfs2?] kernel BUG in ocfs2_move_extents syzbot
     [not found] <20251231075100.287822-1-kartikey406@gmail.com>
2025-12-31 10:25 ` syzbot
     [not found] <20251231075206.287881-1-kartikey406@gmail.com>
2025-12-31 11:25 ` syzbot
     [not found] <20260104114905.12172-1-kartikey406@gmail.com>
2026-01-04 12:13 ` syzbot
     [not found] <20260104122615.13802-1-kartikey406@gmail.com>
2026-01-04 12:50 ` syzbot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=694afc18.050a0220.35954c.0006.GAE@google.com \
    --to=syzbot+7960178e777909060224@syzkaller.appspotmail.com \
    --cc=jlbec@evilplan.org \
    --cc=joseph.qi@linux.alibaba.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@fasheh.com \
    --cc=ocfs2-devel@lists.linux.dev \
    --cc=syzkaller-bugs@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.