From: Alison Schofield <alison.schofield@intel.com>
To: <jianyungao89@gmail.com>
Cc: <linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Dan Williams <djbw@kernel.org>,
Matthew Wilcox <willy@infradead.org>,
Goldwyn Rodrigues <rgoldwyn@suse.com>,
"Darrick J. Wong" <djwong@kernel.org>,
Shiyang Ruan <ruansy.fnst@fujitsu.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"open list:FILESYSTEMS (VFS and infrastructure)"
<linux-fsdevel@vger.kernel.org>,
"open list:FILESYSTEM DIRECT ACCESS (DAX)"
<nvdimm@lists.linux.dev>
Subject: Re: [PATCH v2] dax: fix dax_range_compare_iter() to use correct size and address offset
Date: Thu, 15 Oct 2026 17:51:13 -0700 [thread overview]
Message-ID: <atF1AdT5tF2qWt4T@aschofie-mobl2.lan> (raw)
In-Reply-To: <20261011064840.1296-1-jianyungao89@gmail.com>
On Sun, Oct 11, 2026 at 02:48:39PM +0800, jianyungao89@gmail.com wrote:
> From: Jianyun Gao <jianyungao89@gmail.com>
>
> dax_range_compare_iter() has two bugs in how it calls
> dax_iomap_direct_access() and uses the returned addresses:
>
> 1. The size argument passed to dax_iomap_direct_access() is
> ALIGN(pos + len, PAGE_SIZE), which is an absolute file offset
> rather than a length. This causes the underlying dax_direct_access()
> to request a massively inflated nr_pages via PHYS_PFN(size).
>
> 2. The addresses returned by dax_iomap_direct_access() are page-aligned
> starting addresses, but memcmp() compares from saddr/daddr directly
> without adding the page-in-page offset of pos1/pos2. When pos1/pos2
> are not page-aligned, this compares the wrong data.
>
> Fix the size by computing ALIGN(len + offset_in_page(pos), PAGE_SIZE),
> matching the pattern used in dax_iomap_copy_around(). Fix the address
> by adding offset_in_page(pos1)/offset_in_page(pos2) to saddr/daddr in
> the memcmp() call.
Applied to libnvdimm-for-next:
https://git.kernel.org/nvdimm/nvdimm/c/a4bfbfb4e98a
>
> Fixes: 6f7db3894ae2 ("fsdax: dedup file range to use a compare function")
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Jianyun Gao <jianyungao89@gmail.com>
> ---
>
> Changes in v2:
> - Add offset_in_page(pos1)/offset_in_page(pos2) to the saddr/daddr
> arguments in memcmp() to fix the page-in-page offset issue pointed
> out in the v1 review.
> - Use offset_in_page() macro instead of (pos & ~PAGE_MASK) for
> consistency with the rest of the codebase.
>
> v1: https://lore.kernel.org/lkml/20261010071453.6028-1-jianyungao89@gmail.com/
>
> fs/dax.c | 12 +++++++-----
> 1 file changed, 7 insertions(+), 5 deletions(-)
>
> diff --git a/fs/dax.c b/fs/dax.c
> index 6ba50142eeb2..b08d408418bd 100644
> --- a/fs/dax.c
> +++ b/fs/dax.c
> @@ -2197,6 +2197,7 @@ static int dax_range_compare_iter(struct iomap_iter *it_src,
> const struct iomap *dmap = &it_dest->iomap;
> loff_t pos1 = it_src->pos, pos2 = it_dest->pos;
> void *saddr, *daddr;
> + size_t size1, size2;
> int id, ret;
>
> len = min(len, min(smap->length, dmap->length));
> @@ -2212,17 +2213,18 @@ static int dax_range_compare_iter(struct iomap_iter *it_src,
> }
>
> id = dax_read_lock();
> - ret = dax_iomap_direct_access(smap, pos1, ALIGN(pos1 + len, PAGE_SIZE),
> - &saddr, NULL);
> + size1 = ALIGN(len + offset_in_page(pos1), PAGE_SIZE);
> + ret = dax_iomap_direct_access(smap, pos1, size1, &saddr, NULL);
> if (ret < 0)
> goto out_unlock;
>
> - ret = dax_iomap_direct_access(dmap, pos2, ALIGN(pos2 + len, PAGE_SIZE),
> - &daddr, NULL);
> + size2 = ALIGN(len + offset_in_page(pos2), PAGE_SIZE);
> + ret = dax_iomap_direct_access(dmap, pos2, size2, &daddr, NULL);
> if (ret < 0)
> goto out_unlock;
>
> - *same = !memcmp(saddr, daddr, len);
> + *same = !memcmp(saddr + offset_in_page(pos1),
> + daddr + offset_in_page(pos2), len);
> if (!*same)
> len = 0;
> dax_read_unlock(id);
> --
> 2.34.1
>
>
prev parent reply other threads:[~2026-10-16 0:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-11 6:48 jianyungao89
2026-10-14 12:54 ` Jan Kara
2026-10-16 0:51 ` Alison Schofield [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=atF1AdT5tF2qWt4T@aschofie-mobl2.lan \
--to=alison.schofield@intel.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=djbw@kernel.org \
--cc=djwong@kernel.org \
--cc=jack@suse.cz \
--cc=jianyungao89@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=rgoldwyn@suse.com \
--cc=ruansy.fnst@fujitsu.com \
--cc=stable@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--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
all inboxes | Powered by JetHome®