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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3b8db0e4f263 Linux 5.15.182
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13f53768580000
kernel config: https://syzkaller.appspot.com/x/.config?x=dd5e00a2e31fafd7
dashboard link: https://syzkaller.appspot.com/bug?extid=c71292931fd3fba5a741
compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ff1afedf7b4d/disk-3b8db0e4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/19cb045784cf/vmlinux-3b8db0e4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/43c663d2f6a5/Image-3b8db0e4.gz.xz

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

ocfs2: Mounting device (7,3) on (node local, slot 0) with ordered data mode.
------------[ cut here ]------------
kernel BUG at fs/ocfs2/uptodate.c:509!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 6252 Comm: syz.3.469 Not tainted 5.15.182-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/19/2025
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : ocfs2_set_new_buffer_uptodate+0x150/0x198 fs/ocfs2/uptodate.c:509
lr : ocfs2_set_new_buffer_uptodate+0x150/0x198 fs/ocfs2/uptodate.c:509
sp : ffff8000200f7860
x29: ffff8000200f7860 x28: ffff8000200f7940 x27: ffff70000401ef28
x26: dfff800000000000 x25: ffff8000200f7bb0 x24: ffff0000df1a2e00
x23: 1ffff0000401ef76 x22: 0000000000000000 x21: 0000000000000001
x20: ffff0000e99491d0 x19: ffff0000e9991670 x18: 1fffe0003421f78e
x17: 1fffe0003421f78e x16: ffff8000111a53fc x15: ffff8000141eec20
x14: ffff0001a10fbc80 x13: 1ffff0000282a06b x12: 0000000000080000
x11: 00000000000026cf x10: ffff800025ea9000 x9 : ffff800009d3c384
x8 : 00000000000026d0 x7 : ffff800009c73a3c x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff8000082d4c38
x2 : 0000000000000001 x1 : 0000000000000001 x0 : 0000000000000000
Call trace:
ocfs2_set_new_buffer_uptodate+0x150/0x198 fs/ocfs2/uptodate.c:509
ocfs2_group_add+0x27c/0xe6c fs/ocfs2/resize.c:499
ocfs2_ioctl+0x82c/0xc60 fs/ocfs2/ioctl.c:887
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:874 [inline]
__se_sys_ioctl fs/ioctl.c:860 [inline]
__arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:860
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: a8c47bfd d50323bf d65f03c0 979cf15b (d4210000)
---[ end trace 0eaafbc4209340a0 ]---


---
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

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: 3b8db0e4f263 Linux 5.15.182
git tree: linux-5.15.y

console output: https://syzkaller.appspot.com/x/log.txt?x=10d75670580000

kernel config: https://syzkaller.appspot.com/x/.config?x=dd5e00a2e31fafd7
dashboard link: https://syzkaller.appspot.com/bug?extid=c71292931fd3fba5a741
compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2
userspace arch: arm64

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=163df4d4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1056c2f4580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ff1afedf7b4d/disk-3b8db0e4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/19cb045784cf/vmlinux-3b8db0e4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/43c663d2f6a5/Image-3b8db0e4.gz.xz

mounted in repro: https://storage.googleapis.com/syzbot-assets/1e3402357b50/mount_0.gz
fsck result: OK (log: https://syzkaller.appspot.com/x/fsck.log?x=125d3768580000)

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

option from the mount to silence this warning.
=======================================================
ocfs2: Mounting device (7,0) on (node local, slot 0) with ordered data mode.

------------[ cut here ]------------
kernel BUG at fs/ocfs2/uptodate.c:509!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:

CPU: 0 PID: 4021 Comm: syz-executor151 Not tainted 5.15.182-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/19/2025
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : ocfs2_set_new_buffer_uptodate+0x150/0x198 fs/ocfs2/uptodate.c:509
lr : ocfs2_set_new_buffer_uptodate+0x150/0x198 fs/ocfs2/uptodate.c:509

sp : ffff80001bea7860
x29: ffff80001bea7860 x28: ffff80001bea7940 x27: ffff7000037d4f28
x26: dfff800000000000 x25: ffff80001bea7bb0 x24: ffff0000e2ce8e00
x23: 1ffff000037d4f76 x22: 0000000000000000 x21: 0000000000000001
x20: ffff0000de3323a0 x19: ffff0000de3e4130 x18: 0000000000000000
x17: ffff800016cdf000 x16: ffff8000111a53fc x15: ffff8000167bf4c0
x14: ffff0000ce1c5bc0 x13: dfff800000000000 x12: 0000000000ff0100
x11: 0000000000000000 x10: 0000000000000000 x9 : ffff800009d3c384
x8 : ffff0000ce1c51c0 x7 : 0000000000000000 x6 : 0000000000000000
x5 : ffff800016e187c0 x4 : 0000000000000008 x3 : ffff8000082d4c38

x2 : 0000000000000001 x1 : 0000000000000001 x0 : 0000000000000000
Call trace:
ocfs2_set_new_buffer_uptodate+0x150/0x198 fs/ocfs2/uptodate.c:509
ocfs2_group_add+0x27c/0xe6c fs/ocfs2/resize.c:499
ocfs2_ioctl+0x82c/0xc60 fs/ocfs2/ioctl.c:887
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:874 [inline]
__se_sys_ioctl fs/ioctl.c:860 [inline]
__arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:860
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: a8c47bfd d50323bf d65f03c0 979cf15b (d4210000)

---[ end trace 85c32af5cb618b98 ]---


---
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.