From: syzbot <syzbot+5bdd4953bc58c8fbd6eb@syzkaller.appspotmail.com>
To: dmantipov@yandex.ru, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] kernel BUG in ocfs2_iget
Date: Wed, 22 Oct 2025 12:35:02 -0700 [thread overview]
Message-ID: <68f931e6.a70a0220.3bf6c6.0024.GAE@google.com> (raw)
In-Reply-To: <20251022150431.jNFth%dmantipov@yandex.ru>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
kernel BUG in ocfs2_iget
(syz.0.17,6559,0):ocfs2_read_locked_inode:612 ERROR: Inode 66: system file state is ambiguous
------------[ cut here ]------------
kernel BUG at fs/ocfs2/inode.c:612!
Oops: invalid opcode: 0000 [#1] SMP KASAN PTI
CPU: 0 UID: 0 PID: 6559 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
RIP: 0010:ocfs2_read_locked_inode fs/ocfs2/inode.c:609 [inline]
RIP: 0010:ocfs2_iget+0x19a3/0x1a90 fs/ocfs2/inode.c:157
Code: bc 24 60 01 00 00 4c 8b 84 24 a0 01 00 00 4c 89 f7 48 c7 c6 f0 55 d7 8c ba 64 02 00 00 48 c7 c1 00 c9 0a 8b e8 9e 65 15 00 90 <0f> 0b e8 a6 cb 23 fe 90 0f 0b e8 9e cb 23 fe 31 f6 65 ff 0d 65 3f
RSP: 0018:ffffc90003f66d40 EFLAGS: 00010246
RAX: 8f703e25fe532600 RBX: ffffc90003f66e80 RCX: 8f703e25fe532600
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90003f66fb0 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: ffffed101710487b R12: ffff888044f6642c
R13: 1ffff920007ecdb0 R14: ffffc90003f66ea0 R15: 1000000000000000
FS: 00007f4a52cbe6c0(0000) GS:ffff888127012000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f45247a7000 CR3: 000000003fd50000 CR4: 00000000003526f0
Call Trace:
<TASK>
ocfs2_init_global_system_inodes+0x16c/0x660 fs/ocfs2/super.c:449
ocfs2_initialize_super fs/ocfs2/super.c:2196 [inline]
ocfs2_fill_super+0x447b/0x65f0 fs/ocfs2/super.c:993
get_tree_bdev_flags+0x40e/0x4d0 fs/super.c:1691
vfs_get_tree+0x92/0x2b0 fs/super.c:1751
fc_mount fs/namespace.c:1208 [inline]
do_new_mount_fc fs/namespace.c:3651 [inline]
do_new_mount+0x302/0xa10 fs/namespace.c:3727
do_mount fs/namespace.c:4050 [inline]
__do_sys_mount fs/namespace.c:4238 [inline]
__se_sys_mount+0x313/0x410 fs/namespace.c:4215
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f4a5365066a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 1a 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f4a52cbde68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f4a52cbdef0 RCX: 00007f4a5365066a
RDX: 0000200000004440 RSI: 00002000000000c0 RDI: 00007f4a52cbdeb0
RBP: 0000200000004440 R08: 00007f4a52cbdef0 R09: 00000000000008c0
R10: 00000000000008c0 R11: 0000000000000246 R12: 00002000000000c0
R13: 00007f4a52cbdeb0 R14: 0000000000004446 R15: 0000200000000240
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:ocfs2_read_locked_inode fs/ocfs2/inode.c:609 [inline]
RIP: 0010:ocfs2_iget+0x19a3/0x1a90 fs/ocfs2/inode.c:157
Code: bc 24 60 01 00 00 4c 8b 84 24 a0 01 00 00 4c 89 f7 48 c7 c6 f0 55 d7 8c ba 64 02 00 00 48 c7 c1 00 c9 0a 8b e8 9e 65 15 00 90 <0f> 0b e8 a6 cb 23 fe 90 0f 0b e8 9e cb 23 fe 31 f6 65 ff 0d 65 3f
RSP: 0018:ffffc90003f66d40 EFLAGS: 00010246
RAX: 8f703e25fe532600 RBX: ffffc90003f66e80 RCX: 8f703e25fe532600
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90003f66fb0 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: ffffed101710487b R12: ffff888044f6642c
R13: 1ffff920007ecdb0 R14: ffffc90003f66ea0 R15: 1000000000000000
FS: 00007f4a52cbe6c0(0000) GS:ffff888127012000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f4524799000 CR3: 000000003fd50000 CR4: 00000000003526f0
Tested on:
commit: 552c5071 Merge tag 'vfio-v6.18-rc3' of https://github...
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=12a64614580000
kernel config: https://syzkaller.appspot.com/x/.config?x=b1620e3721dc97c0
dashboard link: https://syzkaller.appspot.com/bug?extid=5bdd4953bc58c8fbd6eb
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=12b19b04580000
next parent reply other threads:[~2025-10-22 19:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251022150431.jNFth%dmantipov@yandex.ru>
2025-10-22 19:35 ` syzbot [this message]
[not found] <8eef8e1578a876b9894ac23e025db861a859491b.camel@yandex.ru>
2026-06-04 6:32 ` syzbot
[not found] <f9eae85cc31b8b02e7fff2e4b610d01ff45bf961.camel@yandex.ru>
2026-06-03 15:42 ` syzbot
[not found] <20240816091139.3070635-1-lizhi.xu@windriver.com>
2024-08-16 9:33 ` syzbot
[not found] <20240816080852.2626448-1-lizhi.xu@windriver.com>
2024-08-16 8:23 ` syzbot
[not found] <20240816072319.3047417-1-lizhi.xu@windriver.com>
2024-08-16 7:45 ` syzbot
[not found] <20240816065432.733582-1-lizhi.xu@windriver.com>
2024-08-16 7:16 ` syzbot
[not found] <20240816061835.50652-1-lizhi.xu@windriver.com>
2024-08-16 6:23 ` syzbot
[not found] <20240816054904.4016904-1-lizhi.xu@windriver.com>
2024-08-16 6:06 ` syzbot
[not found] <20240816032623.3023693-1-lizhi.xu@windriver.com>
2024-08-16 3:41 ` syzbot
2024-08-15 10:47 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=68f931e6.a70a0220.3bf6c6.0024.GAE@google.com \
--to=syzbot+5bdd4953bc58c8fbd6eb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome