From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: Guangshuo Li <lgs201920130244@gmail.com>,
akpm <akpm@linux-foundation.org>
Cc: Mark Fasheh <mark@fasheh.com>, Joel Becker <jlbec@evilplan.org>,
Tristan Ye <tristan.ye@oracle.com>,
ocfs2-devel@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] ocfs2: free unused clusters on defrag move errors
Date: Tue, 21 Jul 2026 09:08:37 +0800 [thread overview]
Message-ID: <a693bbc7-52fb-4efc-a4de-fa597cff24c8@linux.alibaba.com> (raw)
In-Reply-To: <20260720141944.485212-1-lgs201920130244@gmail.com>
On 7/20/26 10:19 PM, Guangshuo Li wrote:
> ocfs2_defrag_extent() claims new clusters before calling
> __ocfs2_move_extent(). If the move fails before ocfs2_split_extent()
> succeeds, the claimed clusters are not referenced by the inode and must
> be released.
>
> The current error path only logs the error and continues to
> ocfs2_cow_sync_writeback(), which can overwrite the original error with
> zero and leave the claimed clusters allocated.
>
> Not every __ocfs2_move_extent() error can free the new clusters. Once
> ocfs2_split_extent() succeeds, the extent tree references them even if
> ocfs2_decrease_refcount() or ocfs2_truncate_log_append() subsequently
> fails. Freeing the clusters in that case would leave the extent tree
> pointing to clusters marked free.
>
> context->new_phys_cpos is updated immediately after a successful extent
> split. Compare it with the newly claimed physical cluster on error. If
> they differ, the split for the current move did not complete and the
> claimed clusters can be freed. If they match, leave the clusters
> allocated because the extent tree already references them.
>
> Return move errors through the transaction cleanup path so that the
> original error is preserved instead of being overwritten by writeback.
>
> Fixes: 202ee5facb2c ("Ocfs2/move_extents: defrag a range of extent.")
> Signed-off-by: Guangshuo Li <lgs201920130244@gmail.com>
Looks fine.
Reviewed-by: Joseph Qi <joseph.qi@linux.alibaba.com>
> ---
> v3:
> - Fix the duplicate split_started declaration.
> - Reuse context->new_phys_cpos to determine whether the extent split
> succeeded, as suggested by Joseph Qi.
> - Avoid changing the __ocfs2_move_extent() prototype.
>
> v2:
> - Do not free the new clusters after the extent-tree update has
> started, as pointed out by Joseph Qi.
> - Track whether the new clusters remain unused on error.
> - Preserve __ocfs2_move_extent() errors instead of allowing the
> subsequent writeback call to overwrite them.
>
> fs/ocfs2/move_extents.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/fs/ocfs2/move_extents.c b/fs/ocfs2/move_extents.c
> index ad1678ee7cc4..7820df90a262 100644
> --- a/fs/ocfs2/move_extents.c
> +++ b/fs/ocfs2/move_extents.c
> @@ -310,8 +310,12 @@ static int ocfs2_defrag_extent(struct ocfs2_move_extents_context *context,
>
> ret = __ocfs2_move_extent(handle, context, cpos, new_len, phys_cpos,
> new_phys_cpos, ext_flags);
> - if (ret)
> + if (ret) {
> mlog_errno(ret);
> + if (context->new_phys_cpos != new_phys_cpos)
> + need_free = 1;
> + goto out_commit;
> + }
>
> if (partial && (new_len != *len))
> *len = new_len;
next prev parent reply other threads:[~2026-07-21 1:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 14:19 Guangshuo Li
2026-07-21 1:08 ` Joseph Qi [this message]
2026-07-21 1:15 ` Andrew Morton
2026-07-21 3:16 ` Joseph Qi
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=a693bbc7-52fb-4efc-a4de-fa597cff24c8@linux.alibaba.com \
--to=joseph.qi@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=jlbec@evilplan.org \
--cc=lgs201920130244@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=tristan.ye@oracle.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®