iomap: add pos and dirty_len into trace_iomap_writepage_map
authorZhang Yi <yi.zhang@huawei.com>
Tue, 20 Feb 2024 11:57:59 +0000 (19:57 +0800)
committerChristian Brauner <brauner@kernel.org>
Wed, 21 Feb 2024 07:35:20 +0000 (08:35 +0100)
commit54943abce0927156ba9909f1a533b25410bfe2ca
treef85e5df8ee99ed436a7309c2a2faa666f180a4e8
parent19871b5c7a003946d3cd4209a348ab7c0df5dbad
iomap: add pos and dirty_len into trace_iomap_writepage_map

Since commit fd07e0aa23c4 ("iomap: map multiple blocks at a time"), we
could map multi-blocks once a time, and the dirty_len indicates the
expected map length, map_len won't large than it. The pos and dirty_len
means the dirty range that should be mapped to write, add them into
trace_iomap_writepage_map() could be more useful for debug.

Signed-off-by: Zhang Yi <yi.zhang@huawei.com>
Link: https://lore.kernel.org/r/20240220115759.3445025-1-yi.zhang@huaweicloud.com
Reviewed-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
Signed-off-by: Christian Brauner <brauner@kernel.org>
fs/iomap/buffered-io.c
fs/iomap/trace.h