UPSTREAM: mm/filemap: fix miscalculated file range for filemap_fdatawrite_range_kick()

iocb->ki_pos has been updated with the number of written bytes since
generic_perform_write().

Besides __filemap_fdatawrite_range() accepts the inclusive end of the
data range.

Bug: 416315033
(cherry picked from commit 8510edf1)
Fixes: 1d445757 ("mm: call filemap_fdatawrite_range_kick() after IOCB_DONTCACHE issue")
Change-Id: Ieb7346e01e9aa712cb7c289bd62e60b6d1db9746
Signed-off-by: Jingbo Xu <jefflexu@linux.alibaba.com>
Link: https://lore.kernel.org/r/20250218120209.88093-2-jefflexu@linux.alibaba.com


Reviewed-by: Jens Axboe <axboe@kernel.dk>
Signed-off-by: Christian Brauner <brauner@kernel.org>
Signed-off-by: Akilesh Kailash <akailash@google.com>