Re: [PATCH v5 0/2] vfs: add FILE_DEDUPE_RANGE_REPORT_PROGRESS flag to FIDEDUPERANGE

[Christian Brauner]

On Sat, 26 Sep 2026 12:38:34 +0800, Matthias Goergens wrote:
> vfs: add FILE_DEDUPE_RANGE_REPORT_PROGRESS flag to FIDEDUPERANGE
> 
> Dedupe tools advance their file offsets by bytes_deduped, but when the
> kernel shortens a request to a block boundary it still reports the
> requested length. Patch 2 adds a flag under which bytes_deduped is what
> the filesystem actually deduplicated. Patch 1 fixes the DAX comparator,
> whose return value would otherwise surface through the flag.
> 
> [...]

Applied to the vfs-7.5.misc branch of the vfs/vfs.git tree.
Patches in the vfs-7.5.misc branch should appear in linux-next soon.

Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.

It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.

Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs-7.5.misc

[1/2] dax: return the comparison error from dax_dedupe_file_range_compare()
      https://git.kernel.org/vfs/vfs/c/1922bdb0b9bb
[2/2] vfs: add FILE_DEDUPE_RANGE_REPORT_PROGRESS flag to FIDEDUPERANGE
      https://git.kernel.org/vfs/vfs/c/847f74d6293b