From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: Heming Zhao <heming.zhao@suse.com>
Cc: ocfs2-devel@lists.linux.dev, linux-kernel@vger.kernel.org,
gautham.ananthakrishna@oracle.com
Subject: Re: [PATCH] ocfs2: fixing global bitmap allocating failure for discontig type
Date: Tue, 1 Apr 2025 19:38:06 +0800 [thread overview]
Message-ID: <e1014674-51a4-4d40-9bc9-0906ffbeadac@linux.alibaba.com> (raw)
In-Reply-To: <20250327062209.19201-1-heming.zhao@suse.com>
On 2025/3/27 14:22, Heming Zhao wrote:
> The commit 4eb7b93e0310 ("ocfs2: improve write IO performance when
> fragmentation is high") introduced a regression. In the discontiguous
> extent allocation case, ocfs2_cluster_group_search() is comparing with
> the wrong target length, which causes allocation failure.
>
> Call stack:
> ocfs2_mkdir()
> ocfs2_reserve_new_inode()
> ocfs2_reserve_suballoc_bits()
> ocfs2_block_group_alloc()
> ocfs2_block_group_alloc_discontig()
> __ocfs2_claim_clusters()
> ocfs2_claim_suballoc_bits()
> ocfs2_search_chain()
> ocfs2_cluster_group_search()
>
> Reported-by: Gautham Ananthakrishna <gautham.ananthakrishna@oracle.com>
> Fixes: 4eb7b93e0310 ("ocfs2: improve write IO performance when fragmentation is high")
> Signed-off-by: Heming Zhao <heming.zhao@suse.com>
> ---
> fs/ocfs2/suballoc.c | 14 +++++++++++---
> fs/ocfs2/suballoc.h | 1 +
> 2 files changed, 12 insertions(+), 3 deletions(-)
>
> diff --git a/fs/ocfs2/suballoc.c b/fs/ocfs2/suballoc.c
> index f7b483f0de2a..3dea082f6e91 100644
> --- a/fs/ocfs2/suballoc.c
> +++ b/fs/ocfs2/suballoc.c
> @@ -698,10 +698,12 @@ static int ocfs2_block_group_alloc(struct ocfs2_super *osb,
>
> bg_bh = ocfs2_block_group_alloc_contig(osb, handle, alloc_inode,
> ac, cl);
> - if (PTR_ERR(bg_bh) == -ENOSPC)
> + if (PTR_ERR(bg_bh) == -ENOSPC) {
> + ac->ac_which = OCFS2_AC_USE_MAIN_DISCONTIG;
> bg_bh = ocfs2_block_group_alloc_discontig(handle,
> alloc_inode,
> ac, cl);
> + }
> if (IS_ERR(bg_bh)) {
> status = PTR_ERR(bg_bh);
> bg_bh = NULL;
> @@ -2365,7 +2367,8 @@ int __ocfs2_claim_clusters(handle_t *handle,
> BUG_ON(ac->ac_bits_given >= ac->ac_bits_wanted);
>
> BUG_ON(ac->ac_which != OCFS2_AC_USE_LOCAL
> - && ac->ac_which != OCFS2_AC_USE_MAIN);
> + && ac->ac_which != OCFS2_AC_USE_MAIN
> + && ac->ac_which != OCFS2_AC_USE_MAIN_DISCONTIG);
>
> if (ac->ac_which == OCFS2_AC_USE_LOCAL) {
> WARN_ON(min_clusters > 1);
> @@ -2427,7 +2430,12 @@ int ocfs2_claim_clusters(handle_t *handle,
> u32 *cluster_start,
> u32 *num_clusters)
> {
> - unsigned int bits_wanted = ac->ac_bits_wanted - ac->ac_bits_given;
> + unsigned int bits_wanted;
> +
> + if (ac->ac_which == OCFS2_AC_USE_MAIN)
> + bits_wanted = ac->ac_bits_wanted - ac->ac_bits_given;
> + else /* ac_which == OCFS2_AC_USE_MAIN_DISCONTIG */
> + bits_wanted = min_clusters;
This looks wried. Why can not be other alloc type?
Or it seems you intend to:
unsigned int bits_wanted = ac->ac_bits_wanted - ac->ac_bits_given;
if (ac->ac_which == OCFS2_AC_USE_MAIN_DISCONTIG)
bits_wanted = min_clusters;
Thanks,
Joseph
>
> return __ocfs2_claim_clusters(handle, ac, min_clusters,
> bits_wanted, cluster_start, num_clusters);
> diff --git a/fs/ocfs2/suballoc.h b/fs/ocfs2/suballoc.h
> index b481b834857d..bcf2ed4a8631 100644
> --- a/fs/ocfs2/suballoc.h
> +++ b/fs/ocfs2/suballoc.h
> @@ -29,6 +29,7 @@ struct ocfs2_alloc_context {
> #define OCFS2_AC_USE_MAIN 2
> #define OCFS2_AC_USE_INODE 3
> #define OCFS2_AC_USE_META 4
> +#define OCFS2_AC_USE_MAIN_DISCONTIG 5
> u32 ac_which;
>
> /* these are used by the chain search */
next prev parent reply other threads:[~2025-04-01 11:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 6:22 Heming Zhao
2025-03-27 6:43 ` Heming Zhao
2025-04-01 11:38 ` Joseph Qi [this message]
2025-04-01 13:50 ` 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=e1014674-51a4-4d40-9bc9-0906ffbeadac@linux.alibaba.com \
--to=joseph.qi@linux.alibaba.com \
--cc=gautham.ananthakrishna@oracle.com \
--cc=heming.zhao@suse.com \
--cc=linux-kernel@vger.kernel.org \
--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®