Hello,
syzbot found the following issue on:
HEAD commit: 344a09659766 Linux 6.1.131
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=17774198580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=14d5dbae75afa499
dashboard link:
https://syzkaller.appspot.com/bug?extid=852b4bb3acd0e4767bbb
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
syz repro:
https://syzkaller.appspot.com/x/repro.syz?x=1215643f980000
C reproducer:
https://syzkaller.appspot.com/x/repro.c?x=1615643f980000
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/8c94453bbad3/disk-344a0965.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/6bf26518c790/vmlinux-344a0965.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/424da9a470eb/Image-344a0965.gz.xz
mounted in repro:
https://storage.googleapis.com/syzbot-assets/e05cd4c2119c/mount_0.gz
fsck result: OK (log:
https://syzkaller.appspot.com/x/fsck.log?x=1554cde4580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+852b4b...@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at fs/ocfs2/journal.c:979!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 5737 Comm: syz-executor488 Not tainted 6.1.131-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : ocfs2_journal_toggle_dirty+0x350/0x354 fs/ocfs2/journal.c:979
lr : ocfs2_journal_toggle_dirty+0x350/0x354 fs/ocfs2/journal.c:979
sp : ffff800023726b40
x29: ffff800023726bc0 x28: 1ffff000046e4db8 x27: 1fffe0001d6c3127
x26: dfff800000000000 x25: 00000000ffffffff x24: 1ffff000046e4d6c
x23: ffff0000e44c4600 x22: 0000000000000000 x21: ffff0000eb618938
x20: ffff0000d36d3420 x19: 0000000000000000 x18: 1fffe0003679c776
x17: ffff800015afd000 x16: ffff8000122dd0e4 x15: 0000000000000000
x14: 000000000000000d x13: ffff0000d31b3780 x12: 0000000000000001
x11: 0000000000ff0100 x10: 0000000000000000 x9 : ffff800009f7fca8
x8 : ffff0000d31b3780 x7 : ffff80000c39b4ac x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : ffff800008b38c2c
x2 : 0000000000000000 x1 : 00000000ffffffff x0 : 0000000000000000
Call trace:
ocfs2_journal_toggle_dirty+0x350/0x354 fs/ocfs2/journal.c:979
ocfs2_journal_wipe+0xec/0x29c fs/ocfs2/journal.c:1165
ocfs2_check_volume fs/ocfs2/super.c:2415 [inline]
ocfs2_mount_volume+0x9a0/0x14a8 fs/ocfs2/super.c:1819
ocfs2_fill_super+0x39c0/0x4a58 fs/ocfs2/super.c:1082
mount_bdev+0x274/0x370 fs/super.c:1443
ocfs2_mount+0x44/0x58 fs/ocfs2/super.c:1186
legacy_get_tree+0xd4/0x16c fs/fs_context.c:632
vfs_get_tree+0x90/0x274 fs/super.c:1573
do_new_mount+0x278/0x8fc fs/namespace.c:3056
path_mount+0x590/0xe5c fs/namespace.c:3386
do_mount fs/namespace.c:3399 [inline]
__do_sys_mount fs/namespace.c:3607 [inline]
__se_sys_mount fs/namespace.c:3584 [inline]
__arm64_sys_mount+0x498/0x588 fs/namespace.c:3584
__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/0x168 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: 97a7df9c 17ffff8a 957e981a 9795d3d6 (d4210000)
---[ end trace 0000000000000000 ]---
---
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 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.
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