From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: CJ <firefly0158@163.com>,
"ocfs2-devel@lists.linux.dev" <ocfs2-devel@lists.linux.dev>
Cc: mark@fasheh.com, jlbec@evilplan.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG] ocfs2: assertion failure in _ocfs2_free_suballoc_bits on a crafted image
Date: Tue, 22 Sep 2026 17:17:42 +0800 [thread overview]
Message-ID: <226c8e43-c943-409d-ae6e-f2f05de6643f@linux.alibaba.com> (raw)
In-Reply-To: <6a202941.4a55.1a0c7aeef7d.Coremail.firefly0158@163.com>
Out-of-date ocfs2-devel maillist, resend to ocfs2-devel@lists.linux.dev.
Joseph
On 9/22/26 1:55 PM, CJ wrote:
>
> Hi,
>
>
>
> I am reporting an issue triggered by a syzkaller reproducer on Linux
> 7.3.0-rc2. The issue is reproducible with HEAD commit
> df2908090cda368b01ff43709f51890076c56157.
>
>
> The reproducer mounts a crafted ocfs2 image with commit= options and then
> removes a directory, which makes ocfs2 evict the inode and release its
> suballocator bits.
>
>
> While freeing the bits, _ocfs2_free_suballoc_bits() reads the group
> descriptor for the target group and checks that the range it is about to
> clear fits within the group's declared bit count. The check fails and
> BUG_ON() terminates the kernel. The call path is ocfs2_evict_inode() ->
> ocfs2_wipe_inode() -> ocfs2_remove_inode() -> ocfs2_free_dinode() ->
> _ocfs2_free_suballoc_bits(), reached from vfs_rmdir() in the unlinkat
> syscall context.
>
>
> This looks like the on-disk group descriptor and the suballocator chain
> disagreeing about the size of the group, so the release range computed from
> the chain falls outside it. Since the image is untrusted input, reporting
> the inconsistency as a filesystem error instead of an assertion would keep
> the kernel alive. I have not determined which of the two metadata sources
> carries the inconsistent value.
>
>
> This failure was reported earlier against the linux-6.1 longterm series at
> https://syzkaller.appspot.com/bug?extid=3b664d98a77a329be77e, and the
> reproducer below is the one from that report. It still reproduces on the
> tested mainline kernel.
>
>
> Reproducer:
>
>
> syz reproducer: https://pastebin.com/raw/9vVANXgZ
> console output: https://pastebin.com/raw/AZMvqBm0
> kernel config: https://syzkaller.appspot.com/text?tag=KernelConfig&x=6a5cbd268406bf43
>
>
> Kernel:
>
>
> HEAD commit: df2908090cda368b01ff43709f51890076c56157
> git tree: mainline
> kernel version: 7.3.0-rc2
> tested tag: v7.3-rc2 (annotated tag object 5e036ce12de91c6fd674dad33b169c6150be2a7a)
>
>
> Let me know if you need more details or testing.
>
>
> Best regards,
> Changjian Liu
next prev parent reply other threads:[~2026-09-22 9:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 5:55 CJ
2026-09-22 9:17 ` Joseph Qi [this message]
2026-09-22 11:31 ` Joseph Qi
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=226c8e43-c943-409d-ae6e-f2f05de6643f@linux.alibaba.com \
--to=joseph.qi@linux.alibaba.com \
--cc=firefly0158@163.com \
--cc=jlbec@evilplan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
/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
all inboxes | Powered by JetHome®