From: syzbot <syzbot+f2107d999290b8166267@syzkaller.appspotmail.com>
To: dmantipov@yandex.ru, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] kernel BUG in __ocfs2_move_extents_range
Date: Fri, 24 Oct 2025 03:22:03 -0700 [thread overview]
Message-ID: <68fb534b.050a0220.346f24.00bd.GAE@google.com> (raw)
In-Reply-To: <20251024071522.EtAA6%dmantipov@yandex.ru>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
kernel BUG in __ocfs2_move_extents_range
ocfs2: Mounting device (7,0) on (node local, slot 0) with writeback data mode.
------------[ cut here ]------------
kernel BUG at fs/ocfs2/suballoc.c:1363!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 5427 Comm: syz.0.17 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/30/2025
pstate: 82400005 (Nzcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=--)
pc : ocfs2_block_group_set_bits+0x510/0x6c4 fs/ocfs2/suballoc.c:1363
lr : ocfs2_block_group_set_bits+0x510/0x6c4 fs/ocfs2/suballoc.c:1363
sp : ffffffc0216171e0
x29: ffffffc021617260 x28: ffffffb8042c2e7c x27: ffffff80df71a740
x26: 0000000000000002 x25: ffffff80e53bc00c x24: ffffff80f209cfb8
x23: dfffffc000000000 x22: 0000000000000168 x21: 0000000000000001
x20: 1ffffff8042c2e40 x19: ffffff80e53bc000 x18: ffffffc011b0fe20
x17: 1ffffff033e18d7e x16: ffffffc0082d0900 x15: 0000000000000000
x14: 00000000fffffffc x13: 0000000000ff0100 x12: 0000000000ff0100
x11: ff00004009c64374 x10: 0000000000000000 x9 : ffffffc009c64374
x8 : ffffff80d06f5340 x7 : 0000000000000000 x6 : ffffffc008dc3fcc
x5 : 0000000000000168 x4 : 0000000000000001 x3 : ffffff80df71a740
x2 : ffffff80e53bc000 x1 : 0000000000000002 x0 : 0000000000000168
Call trace:
ocfs2_block_group_set_bits+0x510/0x6c4 fs/ocfs2/suballoc.c:1363
ocfs2_move_extent fs/ocfs2/move_extents.c:693 [inline]
__ocfs2_move_extents_range+0x208c/0x2aac fs/ocfs2/move_extents.c:866
ocfs2_move_extents+0x314/0x7e0 fs/ocfs2/move_extents.c:933
ocfs2_ioctl_move_extents+0x420/0x5ec fs/ocfs2/move_extents.c:1065
ocfs2_ioctl+0x204/0xaf4 fs/ocfs2/ioctl.c:930
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl fs/ioctl.c:856 [inline]
__arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:856
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x138 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
Code: 17ffff5e 97a116fd d4210000 97a116fb (d4210000)
---[ end trace 0000000000000000 ]---
Tested on:
commit: 8e6e2188 Linux 6.1.157
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15719be2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=848478f4029d639b
dashboard link: https://syzkaller.appspot.com/bug?extid=f2107d999290b8166267
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
userspace arch: arm64
patch: https://syzkaller.appspot.com/x/patch.diff?x=16b69be2580000
next parent reply other threads:[~2025-10-24 10:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251024071522.EtAA6%dmantipov@yandex.ru>
2025-10-24 10:22 ` syzbot [this message]
[not found] <20251024071534.2MOzq%dmantipov@yandex.ru>
2025-10-24 11:07 ` [syzbot] [ocfs2?] kernel BUG in __ocfs2_move_extents_range syzbot
[not found] <20251024071155.pT8us%dmantipov@yandex.ru>
2025-10-24 9:17 ` syzbot
[not found] <20251022140056.5Yda7%dmantipov@yandex.ru>
2025-10-22 14:49 ` syzbot
2025-04-16 2:09 syzbot
2025-08-17 8:12 ` 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=68fb534b.050a0220.346f24.00bd.GAE@google.com \
--to=syzbot+f2107d999290b8166267@syzkaller.appspotmail.com \
--cc=dmantipov@yandex.ru \
--cc=linux-kernel@vger.kernel.org \
--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.