From: "Darrick J. Wong" <djwong@kernel.org>
To: Shiyang Ruan <ruansy.fnst@fujitsu.com>
Cc: linux-fsdevel@vger.kernel.org, nvdimm@lists.linux.dev,
dan.j.williams@intel.com, willy@infradead.org, jack@suse.cz,
akpm@linux-foundation.org
Subject: Re: [PATCH] fsdax: dedupe should compare the min of two iters' length
Date: Wed, 22 Mar 2023 07:44:25 -0700 [thread overview]
Message-ID: <20230322144425.GB11351@frogsfrogsfrogs> (raw)
In-Reply-To: <1679469958-2-1-git-send-email-ruansy.fnst@fujitsu.com>
On Wed, Mar 22, 2023 at 07:25:58AM +0000, Shiyang Ruan wrote:
> In an dedupe corporation iter loop, the length of iomap_iter decreases
> because it implies the remaining length after each iteration. The
> compare function should use the min length of the current iters, not the
> total length.
>
> Fixes: 0e79e3736d54 ("fsdax: dedupe: iter two files at the same time")
> Signed-off-by: Shiyang Ruan <ruansy.fnst@fujitsu.com>
Makese sense,
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
--D
> ---
> fs/dax.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/dax.c b/fs/dax.c
> index 3e457a16c7d1..9800b93ee14d 100644
> --- a/fs/dax.c
> +++ b/fs/dax.c
> @@ -2022,8 +2022,8 @@ int dax_dedupe_file_range_compare(struct inode *src, loff_t srcoff,
>
> while ((ret = iomap_iter(&src_iter, ops)) > 0 &&
> (ret = iomap_iter(&dst_iter, ops)) > 0) {
> - compared = dax_range_compare_iter(&src_iter, &dst_iter, len,
> - same);
> + compared = dax_range_compare_iter(&src_iter, &dst_iter,
> + min(src_iter.len, dst_iter.len), same);
> if (compared < 0)
> return ret;
> src_iter.processed = dst_iter.processed = compared;
> --
> 2.39.2
>
next prev parent reply other threads:[~2023-03-22 14:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 7:25 [PATCH] fsdax: dedupe should compare the min of two iters' length Shiyang Ruan
2023-03-22 14:44 ` Darrick J. Wong [this message]
2023-03-22 23:12 ` Andrew Morton
2023-03-23 6:48 ` Shiyang Ruan
2023-03-23 22:12 ` Andrew Morton
2023-03-24 4:19 ` Shiyang Ruan
2023-03-24 20:34 ` Andrew Morton
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=20230322144425.GB11351@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=ruansy.fnst@fujitsu.com \
--cc=willy@infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).