From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: Prithvi Tambewagh <activprithvi@gmail.com>,
mark@fasheh.com, jlbec@evilplan.org
Cc: ocfs2-devel@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linux.dev, skhan@linuxfoundation.org,
david.hunter.linux@gmail.com, khalid@kernel.org,
syzbot+96d38c6e1655c1420a72@syzkaller.appspotmail.com
Subject: Re: [PATCH v2] ocfs2: fix kernel BUG in ocfs2_find_victim_chain
Date: Mon, 1 Dec 2025 17:56:43 +0800 [thread overview]
Message-ID: <fa898d5b-ac9d-44bf-ab98-a520f89dbc28@linux.alibaba.com> (raw)
In-Reply-To: <20251201092450.84991-1-activprithvi@gmail.com>
On 2025/12/1 17:24, Prithvi Tambewagh wrote:
> syzbot reported a kernel BUG in ocfs2_find_victim_chain() because the
> `cl_next_free_rec` field of the allocation chain list is 0, triggring the
> BUG_ON(!cl->cl_next_free_rec) condition and panicking the kernel.
>
> To fix this, `cl_next_free_rec` is checked inside the caller of
> ocfs2_find_victim_chain() i.e. ocfs2_claim_suballoc_bits() and if it is
> equal to 0, ocfs2_error() is called, to log the corruption and force the
> filesystem into read-only mode, to prevent further damage.
>
> Reported-by: syzbot+96d38c6e1655c1420a72@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=96d38c6e1655c1420a72
> Tested-by: syzbot+96d38c6e1655c1420a72@syzkaller.appspotmail.com
> Cc: stable@vger.kernel.org
> Signed-off-by: Prithvi Tambewagh <activprithvi@gmail.com>
> ---
> v1->v2:
> - Remove extra line before the if statement in patch
> - Add upper limit check for cl->cl_next_free_rec in the if condition
>
> fs/ocfs2/suballoc.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/fs/ocfs2/suballoc.c b/fs/ocfs2/suballoc.c
> index 6ac4dcd54588..1257c39c2c11 100644
> --- a/fs/ocfs2/suballoc.c
> +++ b/fs/ocfs2/suballoc.c
> @@ -1992,6 +1992,13 @@ static int ocfs2_claim_suballoc_bits(struct ocfs2_alloc_context *ac,
> }
>
> cl = (struct ocfs2_chain_list *) &fe->id2.i_chain;
> + if (!le16_to_cpu(cl->cl_next_free_rec) ||
> + le16_to_cpu(cl->cl_next_free_rec) > le16_to_cpu(cl->cl_count)) {
> + status = ocfs2_error(ac->ac_inode->i_sb,
> + "Chain allocator dinode %llu has 0 chains\n",
The log message also has to be updateed. How about:
if (!le16_to_cpu(cl->cl_next_free_rec) ||
le16_to_cpu(cl->cl_next_free_rec) > le16_to_cpu(cl->cl_count)) {
status = ocfs2_error(ac->ac_inode->i_sb,
"Chain allocator dinode %llu has invalid next "
"free chain record %u, but only %u total\n",
(unsigned long long)le64_to_cpu(fe->i_blkno),
le16_to_cpu(cl->cl_next_free_rec),
le16_to_cpu(cl->cl_count));
Joseph
> + (unsigned long long)le64_to_cpu(fe->i_blkno));
> + goto bail;
> + }
>
> victim = ocfs2_find_victim_chain(cl);
> ac->ac_chain = victim;
>
> base-commit: 939f15e640f193616691d3bcde0089760e75b0d3
next prev parent reply other threads:[~2025-12-01 9:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 9:24 [PATCH v2] ocfs2: fix kernel BUG in ocfs2_find_victim_chain Prithvi Tambewagh
2025-12-01 9:56 ` Joseph Qi [this message]
2025-12-01 10:06 ` Prithvi Tambewagh
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=fa898d5b-ac9d-44bf-ab98-a520f89dbc28@linux.alibaba.com \
--to=joseph.qi@linux.alibaba.com \
--cc=activprithvi@gmail.com \
--cc=david.hunter.linux@gmail.com \
--cc=jlbec@evilplan.org \
--cc=khalid@kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=skhan@linuxfoundation.org \
--cc=syzbot+96d38c6e1655c1420a72@syzkaller.appspotmail.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