From: "Darrick J. Wong" <djwong@kernel.org>
To: Jiangshan Yi <yijiangshan@kylinos.cn>
Cc: cem@kernel.org, ljp1205831794@gmail.com,
gaoyingjie@uniontech.com, linux-xfs@vger.kernel.org,
linux-kernel@vger.kernel.org, 13667453960@163.com
Subject: Re: [PATCH] xfs: remove duplicate INO1_WRITTEN check
Date: Mon, 14 Sep 2026 07:52:03 -0700 [thread overview]
Message-ID: <20260914145203.GM6265@frogsfrogsfrogs> (raw)
In-Reply-To: <20260914082111.195006-1-yijiangshan@kylinos.cn>
On Mon, Sep 14, 2026 at 04:21:11PM +0800, Jiangshan Yi wrote:
> Commit a23eca88448e ("xfs: fix exchange-range reflink flag clearing
> issue with INO1_WRITTEN") duplicated commit b2d5a81dae38 ("xfs: fix
> exchange-range reflink flag clearing issue with INO1_WRITTEN"), so
> xmi_can_exchange_reflink_flags() ended up with two identical
> XFS_EXCHMAPS_INO1_WRITTEN checks. The second one is dead code,
> since the first one already returned false. Remove it.
>
> Signed-off-by: Jiangshan Yi <yijiangshan@kylinos.cn>
Not sure why b2d5a81dae38 got committed twice, but yes this patch is
correct.
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
> ---
> fs/xfs/libxfs/xfs_exchmaps.c | 10 ----------
> 1 file changed, 10 deletions(-)
>
> diff --git a/fs/xfs/libxfs/xfs_exchmaps.c b/fs/xfs/libxfs/xfs_exchmaps.c
> index 49eda8d0994d..3efed37cb98a 100644
> --- a/fs/xfs/libxfs/xfs_exchmaps.c
> +++ b/fs/xfs/libxfs/xfs_exchmaps.c
> @@ -959,16 +959,6 @@ xmi_can_exchange_reflink_flags(
> {
> struct xfs_mount *mp = req->ip1->i_mount;
>
> - /*
> - * The INO1_WRITTEN optimization can skip exchanging hole and
> - * unwritten mappings, which means we cannot guarantee that all
> - * shared extents actually moved to the other file. Clearing the
> - * reflink flag of an inode that still holds shared extents breaks
> - * the CoW write path, so refuse to exchange the flags in that case.
> - */
> - if (req->flags & XFS_EXCHMAPS_INO1_WRITTEN)
> - return false;
> -
> /*
> * The INO1_WRITTEN optimization can skip exchanging hole and
> * unwritten mappings, which means we cannot guarantee that all
> --
> 2.25.1
>
>
next prev parent reply other threads:[~2026-09-14 14:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 8:21 Jiangshan Yi
2026-09-14 14:52 ` Darrick J. Wong [this message]
2026-09-16 12:06 ` Carlos Maiolino
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=20260914145203.GM6265@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=13667453960@163.com \
--cc=cem@kernel.org \
--cc=gaoyingjie@uniontech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=ljp1205831794@gmail.com \
--cc=yijiangshan@kylinos.cn \
/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®