From: Heming Zhao <heming.zhao@suse.com>
To: joseph.qi@linux.alibaba.com
Cc: ocfs2-devel@lists.linux.dev, linux-kernel@vger.kernel.org,
gautham.ananthakrishna@oracle.com
Subject: Re: [PATCH v2 0/1] ocfs2: fix discontig allocating issue
Date: Thu, 17 Apr 2025 12:09:44 +0800 [thread overview]
Message-ID: <9ad1e16b-8537-4161-84a6-6f2b4b37dc1f@suse.com> (raw)
In-Reply-To: <20250414060125.19938-1-heming.zhao@suse.com>
Hi Joseph,
ping...
I see the previous patch was dropped by Andrew, but this v2 patch
is still pending for reviewing.
- Heming
On 4/14/25 14:01, Heming Zhao wrote:
> When running ocfs2-test, I found the same issue [1] regarding
> discontiguous extent allocation. The previous patch [1]'s commit
> is incorrect, and the fix code is insufficient, so I am sending
> this patch.
>
> PS, there is an ocfs2-test PR [2] pending for review.
>
> [1]:
> https://lore.kernel.org/ocfs2-devel/1f3049dc-5536-4a27-8768-b264be062f7c@linux.alibaba.com/T/#t
>
> [2]:
> https://github.com/markfasheh/ocfs2-test/pull/21
>
> ---
> v1 -> v2.
> - we will recall patch [1], so this patch merges some codes of patch [1].
> - polish the 'if' condition in function ocfs2_search_chain().
>
> ---
> Heming Zhao (1):
> ocfs2: fix the issue with discontiguous allocation in the
> global_bitmap
>
> fs/ocfs2/suballoc.c | 38 ++++++++++++++++++++++++++++++++------
> fs/ocfs2/suballoc.h | 1 +
> 2 files changed, 33 insertions(+), 6 deletions(-)
>
prev parent reply other threads:[~2025-04-17 4:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 6:01 Heming Zhao
2025-04-14 6:01 ` [PATCH v2 1/1] ocfs2: fix the issue with discontiguous allocation in the global_bitmap Heming Zhao
2025-04-17 11:11 ` Joseph Qi
2025-04-17 4:09 ` Heming Zhao [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=9ad1e16b-8537-4161-84a6-6f2b4b37dc1f@suse.com \
--to=heming.zhao@suse.com \
--cc=gautham.ananthakrishna@oracle.com \
--cc=joseph.qi@linux.alibaba.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®