From: Heming Zhao <heming.zhao@suse.com>
To: Joseph Qi <joseph.qi@linux.alibaba.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Mark Fasheh <mark@fasheh.com>, Joel Becker <jlbec@evilplan.org>,
ocfs2-devel@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] ocfs2: validate suballoc bit during inode read
Date: Mon, 31 Aug 2026 22:03:41 +0800 [thread overview]
Message-ID: <apWJqcgBV5UPqJYM@p15> (raw)
In-Reply-To: <20260831062848.2743436-3-joseph.qi@linux.alibaba.com>
On Mon, Aug 31, 2026 at 02:28:46PM +0800, Joseph Qi wrote:
> i_suballoc_bit of a dinode is currently not validated at all. A
> corrupted dinode can carry an abnormally large i_suballoc_bit, which
> bypasses ocfs2_validate_inode_block(). When the inode is deleted,
> ocfs2_remove_inode() calls ocfs2_free_dinode(), which passes the
> unvalidated bit to _ocfs2_free_suballoc_bits() and triggers
> BUG_ON((count + start_bit) > ocfs2_bits_per_group(cl)).
>
> Since suballocator block group bitmaps are contained in a single
> block, a valid suballoc bit must be smaller than the number of bits
> per block. Reject oversized i_suballoc_bit values during dinode
> validation.
>
> Signed-off-by: Joseph Qi <joseph.qi@linux.alibaba.com>
LGTM.
Reviewed-by: Heming Zhao <heming.zhao@suse.com>
> ---
> fs/ocfs2/inode.c | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/fs/ocfs2/inode.c b/fs/ocfs2/inode.c
> index eda50f13ffb5..a982c99a9678 100644
> --- a/fs/ocfs2/inode.c
> +++ b/fs/ocfs2/inode.c
> @@ -1543,6 +1543,20 @@ int ocfs2_validate_inode_block(struct super_block *sb,
> goto bail;
> }
>
> + /*
> + * A suballocator block group bitmap is contained in a single block,
> + * so a valid suballoc bit can never exceed the number of bits per
> + * block. Otherwise deleting the inode will pass the oversized bit
> + * to _ocfs2_free_suballoc_bits() via ocfs2_free_dinode() and trigger
> + * BUG_ON((count + start_bit) > ocfs2_bits_per_group(cl)).
> + */
> + if (le16_to_cpu(di->i_suballoc_bit) >= sb->s_blocksize * 8) {
> + rc = ocfs2_error(sb, "Invalid dinode %llu: suballoc bit %u\n",
> + (unsigned long long)bh->b_blocknr,
> + le16_to_cpu(di->i_suballoc_bit));
> + goto bail;
> + }
> +
> if ((le32_to_cpu(di->i_flags) & OCFS2_ORPHANED_FL) &&
> le16_to_cpu(di->i_orphaned_slot) >= OCFS2_SB(sb)->max_slots) {
> rc = ocfs2_error(sb, "Invalid dinode %llu: orphaned slot %u\n",
> --
> 2.39.3
>
next prev parent reply other threads:[~2026-08-31 14:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 6:28 [PATCH 0/4] ocfs2: validate suballoc slot and bit of metadata blocks Joseph Qi
2026-08-31 6:28 ` [PATCH 1/4] ocfs2: restrict OCFS2_INVALID_SLOT suballoc slot to system inodes Joseph Qi
2026-08-31 14:02 ` Heming Zhao
2026-09-01 1:08 ` Joseph Qi
2026-09-01 1:16 ` Heming Zhao
2026-09-01 2:08 ` Joseph Qi
2026-08-31 6:28 ` [PATCH 2/4] ocfs2: validate suballoc bit during inode read Joseph Qi
2026-08-31 14:03 ` Heming Zhao [this message]
2026-08-31 6:28 ` [PATCH 3/4] ocfs2: validate suballoc slot of xattr and dir index blocks Joseph Qi
2026-08-31 14:04 ` Heming Zhao
2026-08-31 6:28 ` [PATCH 4/4] ocfs2: validate suballoc slot of extent blocks Joseph Qi
2026-08-31 14:04 ` Heming Zhao
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=apWJqcgBV5UPqJYM@p15 \
--to=heming.zhao@suse.com \
--cc=akpm@linux-foundation.org \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.