From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: Heming Zhao <heming.zhao@suse.com>,
ocfs2-devel@lists.linux.dev, akpm <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] ocfs2: fix the space leak in LA when releasing LA
Date: Thu, 5 Dec 2024 19:11:50 +0800 [thread overview]
Message-ID: <e30b2754-0d1f-4796-8690-1ad4a6192f44@linux.alibaba.com> (raw)
In-Reply-To: <2a72a270-e551-4529-b900-c955cd378ef8@linux.alibaba.com>
On 12/5/24 7:10 PM, Joseph Qi wrote:
>
>
> On 12/5/24 6:48 PM, Heming Zhao wrote:
>> Commit 30dd3478c3cd ("ocfs2: correctly use ocfs2_find_next_zero_bit()")
>> introduced an issue, the ocfs2_sync_local_to_main() ignores the last
>> contiguous free bits, which causes an OCFS2 volume to lose the last free
>> clusters of LA window during the release routine.
>>
>> Please note, because commit dfe6c5692fb5 ("ocfs2: fix the la space leak
>> when unmounting an ocfs2 volume") was reverted, this commit is a
>> replacement fix for commit dfe6c5692fb5.
>>
>> Fixes: 30dd3478c3cd ("ocfs2: correctly use ocfs2_find_next_zero_bit()")
>> Signed-off-by: Heming Zhao <heming.zhao@suse.com>
>> Suggested-by: Joseph Qi <joseph.qi@linux.alibaba.com>
>
> Reviewed-by: Joseph Qi <joseph.qi@linux.alibaba.com>
Cc: <stable@vger.kernel.org> # 6.10+
>> ---
>> fs/ocfs2/localalloc.c | 8 +++++---
>> 1 file changed, 5 insertions(+), 3 deletions(-)
>>
>> diff --git a/fs/ocfs2/localalloc.c b/fs/ocfs2/localalloc.c
>> index 5df34561c551..d1aa04a5af1b 100644
>> --- a/fs/ocfs2/localalloc.c
>> +++ b/fs/ocfs2/localalloc.c
>> @@ -971,9 +971,9 @@ static int ocfs2_sync_local_to_main(struct ocfs2_super *osb,
>> start = count = 0;
>> left = le32_to_cpu(alloc->id1.bitmap1.i_total);
>>
>> - while ((bit_off = ocfs2_find_next_zero_bit(bitmap, left, start)) <
>> - left) {
>> - if (bit_off == start) {
>> + while (1) {
>> + bit_off = ocfs2_find_next_zero_bit(bitmap, left, start);
>> + if ((bit_off < left) && (bit_off == start)) {
>> count++;
>> start++;
>> continue;
>> @@ -998,6 +998,8 @@ static int ocfs2_sync_local_to_main(struct ocfs2_super *osb,
>> }
>> }
>>
>> + if (bit_off >= left)
>> + break;
>> count = 1;
>> start = bit_off + 1;
>> }
>
prev parent reply other threads:[~2024-12-05 11:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 10:48 [PATCH v2 0/2] Revert ocfs2 commit dfe6c5692fb5 and provide a new fix Heming Zhao
2024-12-05 10:48 ` [PATCH v2 1/2] ocfs2: Revert "ocfs2: fix the la space leak when unmounting an ocfs2 volume" Heming Zhao
2024-12-05 11:09 ` Joseph Qi
2024-12-05 10:48 ` [PATCH v2 2/2] ocfs2: fix the space leak in LA when releasing LA Heming Zhao
2024-12-05 11:10 ` Joseph Qi
2024-12-05 11:11 ` 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=e30b2754-0d1f-4796-8690-1ad4a6192f44@linux.alibaba.com \
--to=joseph.qi@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--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®