Hello,
syzbot found 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=10a169c0580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=a6b3013b6f1a102b
dashboard link:
https://syzkaller.appspot.com/bug?extid=647084ad32e990962697
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/731bd13b5412/disk-0a51d2d4.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/a53b07f54a18/vmlinux-0a51d2d4.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/5f1392034bb8/Image-0a51d2d4.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+647084...@syzkaller.appspotmail.com
(syz.0.65,4386,0):ocfs2_read_locked_inode:536 ERROR: bug expression: !!(fe->i_flags & cpu_to_le32(OCFS2_SYSTEM_FL)) != !!(args->fi_flags & OCFS2_FI_FLAG_SYSFILE)
(syz.0.65,4386,1):ocfs2_read_locked_inode:536 ERROR: Inode 21: system file state is ambiguous
------------[ cut here ]------------
kernel BUG at fs/ocfs2/inode.c:536!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 4386 Comm: syz.0.65 Not tainted 5.15.173-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : ocfs2_read_locked_inode fs/ocfs2/inode.c:533 [inline]
pc : ocfs2_iget+0x1c48/0x1e94 fs/ocfs2/inode.c:159
lr : ocfs2_read_locked_inode fs/ocfs2/inode.c:533 [inline]
lr : ocfs2_iget+0x1c48/0x1e94 fs/ocfs2/inode.c:159
sp : ffff800020466ac0
x29: ffff800020466d00 x28: ffff70000408cd60 x27: dfff800000000000
x26: 0000000000000000 x25: ffff0000ebe2da00 x24: 1ffff0000408cd70
x23: dfff800000000000 x22: 1000000000000000 x21: ffff800020466c00
x20: ffff800020466c60 x19: ffff800020466c20 x18: 0000000000000001
x17: 0000000000000002 x16: ffff800011ab8a34 x15: 00000000ffffffff
x14: ffff0000f51051c0 x13: 0000000000000001 x12: 0000000000080000
x11: 000000000004e417 x10: ffff80002157b000 x9 : f5bc7ca8d5a8c400
x8 : f5bc7ca8d5a8c400 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff8000204660f8 x4 : ffff800014ba05e0 x3 : ffff800008555e80
x2 : 0000000000000001 x1 : 0000000100000000 x0 : 000000000000005d
Call trace:
ocfs2_read_locked_inode fs/ocfs2/inode.c:533 [inline]
ocfs2_iget+0x1c48/0x1e94 fs/ocfs2/inode.c:159
_ocfs2_get_system_file_inode fs/ocfs2/sysfile.c:142 [inline]
ocfs2_get_system_file_inode+0x304/0x6b8 fs/ocfs2/sysfile.c:112
ocfs2_init_global_system_inodes+0x2bc/0x618 fs/ocfs2/super.c:458
ocfs2_initialize_super fs/ocfs2/super.c:2276 [inline]
ocfs2_fill_super+0x394c/0x498c fs/ocfs2/super.c:995
mount_bdev+0x274/0x370 fs/super.c:1400
ocfs2_mount+0x44/0x58 fs/ocfs2/super.c:1187
legacy_get_tree+0xd4/0x16c fs/fs_context.c:611
vfs_get_tree+0x90/0x274 fs/super.c:1530
do_new_mount+0x278/0x8fc fs/namespace.c:3012
path_mount+0x594/0x101c fs/namespace.c:3342
do_mount fs/namespace.c:3355 [inline]
__do_sys_mount fs/namespace.c:3563 [inline]
__se_sys_mount fs/namespace.c:3540 [inline]
__arm64_sys_mount+0x510/0x5e0 fs/namespace.c:3540
__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+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: 913e8063 aa1303e0 52804302 94052186 (d4210000)
---[ end trace 83f083d617b89368 ]---
---
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