From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: Kyle Zeng <kylebot@openai.com>, akpm <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Mark Fasheh <mark@fasheh.com>,
Joel Becker <jlbec@evilplan.org>,
outbounddisclosures@openai.com,
"ocfs2-devel@lists.linux.dev" <ocfs2-devel@lists.linux.dev>,
Heming Zhao <heming.zhao@suse.com>
Subject: Re: [PATCH] ocfs2: avoid moving extents to occupied clusters
Date: Fri, 12 Jun 2026 09:58:47 +0800 [thread overview]
Message-ID: <ccb62980-f0a7-4233-900e-98a57b7cb49b@linux.alibaba.com> (raw)
In-Reply-To: <20260611213510.16956-1-kylebot@openai.com>
On 6/12/26 5:35 AM, Kyle Zeng wrote:
> For non-auto OCFS2_IOC_MOVE_EXT operations, userspace supplies a
> physical me_goal. ocfs2_move_extent() initializes new_phys_cpos from
> that goal and expects ocfs2_probe_alloc_group() to replace it with a
> free run in the target block group.
>
> The probe currently leaves *phys_cpos unchanged if the scan reaches the
> end of the group without finding a free run. An occupied goal at the
> last bit can therefore survive the probe and be passed to
> __ocfs2_move_extent(), which copies file data into a cluster still owned
> by another inode before the bitmap is updated.
>
> When the probe does find a free run, it also subtracts move_len from the
> ending bit. The start of an N-bit run ending at i is i - N + 1, so the
> current calculation can report the bit immediately before the free run.
>
> Clear *phys_cpos before scanning and use the correct free-run start.
> Callers already treat a zero result as -ENOSPC, so failed probes no
> longer continue with an occupied caller-controlled goal.
>
> Fixes: e6b5859cccfa ("Ocfs2/move_extents: helper to probe a proper region to move in an alloc group.")
> Fixes: 236b9254f8d1 ("ocfs2: fix non-auto defrag path not working issue")
> Cc: stable@vger.kernel.org
> Assisted-by: Codex:gpt-5.5
> Signed-off-by: Kyle Zeng <kylebot@openai.com>
Looks fine.
Reviewed-by: Joseph Qi <joseph.qi@linux.alibaba.com>
> ---
> fs/ocfs2/move_extents.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/fs/ocfs2/move_extents.c b/fs/ocfs2/move_extents.c
> index c53de4439d93..ad1678ee7cc4 100644
> --- a/fs/ocfs2/move_extents.c
> +++ b/fs/ocfs2/move_extents.c
> @@ -534,6 +534,8 @@ static void ocfs2_probe_alloc_group(struct inode *inode, struct buffer_head *bh,
> u32 base_cpos = ocfs2_blocks_to_clusters(inode->i_sb,
> le64_to_cpu(gd->bg_blkno));
>
> + *phys_cpos = 0;
> +
> for (i = base_bit; i < le16_to_cpu(gd->bg_bits); i++) {
>
> used = ocfs2_test_bit(i, (unsigned long *)gd->bg_bitmap);
> @@ -555,7 +557,7 @@ static void ocfs2_probe_alloc_group(struct inode *inode, struct buffer_head *bh,
> last_free_bits++;
>
> if (last_free_bits == move_len) {
> - i -= move_len;
> + i = i - move_len + 1;
> *goal_bit = i;
> *phys_cpos = base_cpos + i;
> break;
prev parent reply other threads:[~2026-06-12 1:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 21:35 Kyle Zeng
2026-06-12 1:58 ` 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=ccb62980-f0a7-4233-900e-98a57b7cb49b@linux.alibaba.com \
--to=joseph.qi@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=heming.zhao@suse.com \
--cc=jlbec@evilplan.org \
--cc=kylebot@openai.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=outbounddisclosures@openai.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®