From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: Deepanshu Kartikey <kartikey406@gmail.com>,
mark@fasheh.com, jlbec@evilplan.org,
Heming Zhao <heming.zhao@suse.com>
Cc: ocfs2-devel@lists.linux.dev, linux-kernel@vger.kernel.org,
syzbot+7960178e777909060224@syzkaller.appspotmail.com
Subject: Re: [PATCH] ocfs2: add check for free bits before allocation in ocfs2_move_extent()
Date: Sun, 4 Jan 2026 09:50:00 +0800 [thread overview]
Message-ID: <5563a638-6acd-46cf-b78a-75c4e7a8e836@linux.alibaba.com> (raw)
In-Reply-To: <20251231115801.293726-1-kartikey406@gmail.com>
On 2025/12/31 19:58, Deepanshu Kartikey wrote:
> Add a check to verify the group descriptor has enough free bits before
> attempting allocation in ocfs2_move_extent(). This prevents a kernel
> BUG_ON crash in ocfs2_block_group_set_bits() when the move_extents ioctl
> is called on a crafted or corrupted filesystem.
>
> The existing validation in ocfs2_validate_gd_self() only checks static
> metadata consistency (bg_free_bits_count <= bg_bits) when the descriptor
> is first read from disk. However, during move_extents operations,
> multiple allocations can exhaust the free bits count below the requested
> allocation size, triggering BUG_ON(le16_to_cpu(bg->bg_free_bits_count)
> num_bits).
BUG_ON(le16_to_cpu(bg->bg_free_bits_count) < num_bits)
Seems '<' is missing.
>
> The debug trace shows the issue clearly:
> - Block group 32 validated with bg_free_bits_count=427
> - Repeated allocations decreased count: 427 -> 171 -> 43 -> ... -> 1
> - Final request for 2 bits with only 1 available triggers BUG_ON
>
> By adding an early check in ocfs2_move_extent() before calling
> ocfs2_block_group_set_bits(), we return -ENOSPC gracefully instead of
> crashing the kernel.
>
> Reported-by: syzbot+7960178e777909060224@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=7960178e777909060224
> Tested-by: syzbot+7960178e777909060224@syzkaller.appspotmail.com
> Signed-off-by: Deepanshu Kartikey <kartikey406@gmail.com>
> ---
> fs/ocfs2/move_extents.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/fs/ocfs2/move_extents.c b/fs/ocfs2/move_extents.c
> index 99637e34d9da..2548a8908a1b 100644
> --- a/fs/ocfs2/move_extents.c
> +++ b/fs/ocfs2/move_extents.c
> @@ -690,6 +690,11 @@ static int ocfs2_move_extent(struct ocfs2_move_extents_context *context,
> goto out_commit;
> }
>
> + if (le16_to_cpu(gd->bg_free_bits_count) < len) {
> + ret = -ENOSPC;
> + goto out_commit;
> + }
> +
Why not check rightly after ocfs2_find_victim_alloc_group()?
Joseph
> ret = ocfs2_block_group_set_bits(handle, gb_inode, gd, gd_bh,
> goal_bit, len, 0, 0);
> if (ret) {
prev parent reply other threads:[~2026-01-04 1:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-31 11:58 Deepanshu Kartikey
2026-01-04 1:50 ` Joseph Qi [this message]
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=5563a638-6acd-46cf-b78a-75c4e7a8e836@linux.alibaba.com \
--to=joseph.qi@linux.alibaba.com \
--cc=heming.zhao@suse.com \
--cc=jlbec@evilplan.org \
--cc=kartikey406@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=syzbot+7960178e777909060224@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
all inboxes | Powered by JetHome®