mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: Deepanshu Kartikey <kartikey406@gmail.com>
Cc: ocfs2-devel@lists.linux.dev, linux-kernel@vger.kernel.org,
	syzbot+44c564a3cb08605f34a1@syzkaller.appspotmail.com,
	Joel Becker <jlbec@evilplan.org>, Mark Fasheh <mark@fasheh.com>,
	Heming Zhao <heming.zhao@suse.com>
Subject: Re: [PATCH] ocfs2: validate allocator type to prevent BUG_ON in ocfs2_block_group_search
Date: Thu, 8 Jan 2026 16:25:14 +0800	[thread overview]
Message-ID: <10be03f1-1ab1-44d0-b9c8-89cfc668c304@linux.alibaba.com> (raw)
In-Reply-To: <20260104014028.305029-1-kartikey406@gmail.com>



On 2026/1/4 09:40, Deepanshu Kartikey wrote:
> A corrupted filesystem image can have an inode allocator with the
> OCFS2_BITMAP_FL flag incorrectly set, making ocfs2_is_cluster_bitmap()
> return true. When the code later calls ocfs2_block_group_search(),
> it triggers BUG_ON(ocfs2_is_cluster_bitmap(inode)) causing a kernel panic.
> 
But ocfs2_is_cluster_bitmap() checks ip_blkno.

Thanks,
Joseph

> Call trace:
>   ocfs2_block_group_search+0x1c7/0x2c0 fs/ocfs2/suballoc.c:1611
>   ocfs2_search_chain+0x38a/0x1010 fs/ocfs2/suballoc.c:1764
>   ocfs2_claim_suballoc_bits+0x3a4/0x650 fs/ocfs2/suballoc.c:1978
>   ocfs2_claim_new_inode+0x95/0x130 fs/ocfs2/suballoc.c:2137
>   ocfs2_mknod_locked+0x129/0x510 fs/ocfs2/namei.c:568
>   ocfs2_mknod+0x5c7/0x11d0 fs/ocfs2/namei.c:802
>   ocfs2_create+0x136/0x170 fs/ocfs2/namei.c:852
> 
> Add validation in ocfs2_reserve_suballoc_bits() to check that the
> allocator inode type matches the expected type:
> - Global bitmap allocator must have OCFS2_BITMAP_FL flag set
> - Other allocators (inode, extent) must NOT have OCFS2_BITMAP_FL set
> 
> This follows the existing pattern of validating OCFS2_CHAIN_FL in the
> same function and uses ocfs2_error() for graceful error handling.
> 
> Reported-by: syzbot+44c564a3cb08605f34a1@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=44c564a3cb08605f34a1
> Tested-by: syzbot+44c564a3cb08605f34a1@syzkaller.appspotmail.com
> Signed-off-by: Deepanshu Kartikey <kartikey406@gmail.com>
> ---
>  fs/ocfs2/suballoc.c | 20 ++++++++++++++++++++
>  1 file changed, 20 insertions(+)
> 
> diff --git a/fs/ocfs2/suballoc.c b/fs/ocfs2/suballoc.c
> index 8e6e5235b30c..fb72c062a8d5 100644
> --- a/fs/ocfs2/suballoc.c
> +++ b/fs/ocfs2/suballoc.c
> @@ -813,6 +813,26 @@ static int ocfs2_reserve_suballoc_bits(struct ocfs2_super *osb,
>  		goto bail;
>  	}
>  
> +	/*
> +	 * Validate allocator type matches expected bitmap type.
> +	 * Global bitmap must have BITMAP flag, other allocators must not.
> +	 * This prevents a corrupted filesystem from triggering BUG_ON
> +	 * in ocfs2_block_group_search() or ocfs2_cluster_group_search().
> +	 */
> +	if (type == GLOBAL_BITMAP_SYSTEM_INODE) {
> +		if (!ocfs2_is_cluster_bitmap(alloc_inode)) {
> +			status = ocfs2_error(alloc_inode->i_sb,
> +					     "Global bitmap %llu missing bitmap flag\n",
> +					     (unsigned long long)le64_to_cpu(fe->i_blkno));
> +			goto bail;
> +		}
> +	} else if (ocfs2_is_cluster_bitmap(alloc_inode)) {
> +		status = ocfs2_error(alloc_inode->i_sb,
> +				     "Allocator %llu has invalid bitmap flag\n",
> +				     (unsigned long long)le64_to_cpu(fe->i_blkno));
> +		goto bail;
> +	}
> +
>  	free_bits = le32_to_cpu(fe->id1.bitmap1.i_total) -
>  		le32_to_cpu(fe->id1.bitmap1.i_used);
>  


  reply	other threads:[~2026-01-08  8:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-04  1:40 Deepanshu Kartikey
2026-01-08  8:25 ` Joseph Qi [this message]
2026-01-10  5:38   ` Deepanshu Kartikey

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=10be03f1-1ab1-44d0-b9c8-89cfc668c304@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+44c564a3cb08605f34a1@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®