[v5.15] kernel BUG in __ocfs2_flush_truncate_log

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3a5928702e71 Linux 5.15.167
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=104317c7980000
kernel config: https://syzkaller.appspot.com/x/.config?x=4d3fd5cca89ae935
dashboard link: https://syzkaller.appspot.com/bug?extid=e8dae693d1041bee4f51
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ef5025f3d708/disk-3a592870.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/776fbdad3aa8/vmlinux-3a592870.xz
kernel image: https://storage.googleapis.com/syzbot-assets/79541db5bd16/bzImage-3a592870.xz

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

------------[ cut here ]------------
kernel BUG at fs/ocfs2/alloc.c:6002!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 155 Comm: kworker/u4:3 Not tainted 5.15.167-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
Workqueue: ocfs2_wq ocfs2_truncate_log_worker
RIP: 0010:__ocfs2_flush_truncate_log+0x1077/0x11c0 fs/ocfs2/alloc.c:6002
Code: ff 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c 8a fb ff ff 48 89 df e8 4a 31 9a fe e9 7d fb ff ff e8 c0 66 50 fe 0f 0b e8 b9 66 50 fe <0f> 0b 65 44 8b 2d 97 21 d2 7c bf 07 00 00 00 44 89 ee e8 02 6a 50
RSP: 0000:ffffc900020579a0 EFLAGS: 00010293
RAX: ffffffff832ff3b7 RBX: 00000000ffffffff RCX: ffff88801e100000
RDX: 0000000000000000 RSI: 00000000ffffffff RDI: 0000000000000000
RBP: ffffc90002057bb0 R08: ffffffff832fe50e R09: fffff5200040af1d
R10: 0000000000000000 R11: dffffc0000000001 R12: ffffc90002057ac0
R13: ffff8880743516b8 R14: ffff888059662a00 R15: ffff888064008c00
FS: 0000000000000000(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b32d1aff8 CR3: 000000002866d000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ocfs2_flush_truncate_log fs/ocfs2/alloc.c:6067 [inline]
ocfs2_truncate_log_worker+0x9e/0x1b0 fs/ocfs2/alloc.c:6080
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2310
worker_thread+0xaca/0x1280 kernel/workqueue.c:2457
kthread+0x3f6/0x4f0 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
Modules linked in:
---[ end trace b0ab1b590e671a63 ]---
RIP: 0010:__ocfs2_flush_truncate_log+0x1077/0x11c0 fs/ocfs2/alloc.c:6002
Code: ff 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c 8a fb ff ff 48 89 df e8 4a 31 9a fe e9 7d fb ff ff e8 c0 66 50 fe 0f 0b e8 b9 66 50 fe <0f> 0b 65 44 8b 2d 97 21 d2 7c bf 07 00 00 00 44 89 ee e8 02 6a 50
RSP: 0000:ffffc900020579a0 EFLAGS: 00010293
RAX: ffffffff832ff3b7 RBX: 00000000ffffffff RCX: ffff88801e100000
RDX: 0000000000000000 RSI: 00000000ffffffff RDI: 0000000000000000
RBP: ffffc90002057bb0 R08: ffffffff832fe50e R09: fffff5200040af1d
R10: 0000000000000000 R11: dffffc0000000001 R12: ffffc90002057ac0
R13: ffff8880743516b8 R14: ffff888059662a00 R15: ffff888064008c00
FS: 0000000000000000(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffcf5e70fd8 CR3: 000000000c68e000 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

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: 0a51d2d4527b Linux 5.15.173
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=174c20df980000
kernel config: https://syzkaller.appspot.com/x/.config?x=48dad5136d11d5fc

dashboard link: https://syzkaller.appspot.com/bug?extid=e8dae693d1041bee4f51
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=112cbf78580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=128da7c0580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/df502ed32946/disk-0a51d2d4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a6f49f24ceaa/vmlinux-0a51d2d4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f45db4b68abf/bzImage-0a51d2d4.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/9bd66669d953/mount_0.gz

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

------------[ cut here ]------------
kernel BUG at fs/ocfs2/alloc.c:6002!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN

CPU: 0 PID: 1198 Comm: kworker/u4:3 Not tainted 5.15.173-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024

Workqueue: ocfs2_wq ocfs2_truncate_log_worker
RIP: 0010:__ocfs2_flush_truncate_log+0x1077/0x11c0 fs/ocfs2/alloc.c:6002

Code: ff 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c 8a fb ff ff 48 89 df e8 4a 2a 90 fe e9 7d fb ff ff e8 a0 51 46 fe 0f 0b e8 99 51 46 fe <0f> 0b 65 44 8b 2d 47 f3 c7 7c bf 07 00 00 00 44 89 ee e8 e2 54 46
RSP: 0018:ffffc90004bd79a0 EFLAGS: 00010293
RAX: ffffffff833a2207 RBX: 00000000ffffffff RCX: ffff888022ad5940

RDX: 0000000000000000 RSI: 00000000ffffffff RDI: 0000000000000000

RBP: ffffc90004bd7bb0 R08: ffffffff833a135e R09: fffff5200097af1d
R10: 0000000000000000 R11: dffffc0000000001 R12: ffffc90004bd7ac0
R13: ffff888074b0b338 R14: ffff88806e37ca00 R15: ffff888024491800
FS: 0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000

CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 0000000020771000 CR3: 0000000079d1a000 CR4: 00000000003506f0

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ocfs2_flush_truncate_log fs/ocfs2/alloc.c:6067 [inline]
ocfs2_truncate_log_worker+0x9e/0x1b0 fs/ocfs2/alloc.c:6080
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2310
worker_thread+0xaca/0x1280 kernel/workqueue.c:2457
kthread+0x3f6/0x4f0 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
Modules linked in:


---

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.