Skip to contentSkip to conversation

Patch "iomap: Fix iomap_invalidatepage tracepoint" has been added to the 5.17-stable tree

PATCH Sasha Levin 1 participant 1 message Apr 2, 2022

Subsystems (2)
lore
Share & tools
lore

Sasha Levin

author Applied
#0 lore raw

This is a note to let you know that I've just added the patch titled

iomap: Fix iomap_invalidatepage tracepoint

to the 5.17-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
iomap-fix-iomap_invalidatepage-tracepoint.patch
and it can be found in the queue-5.17 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.

commit 8f9b67c3d57e4cabb1f03a0e28a806b082cd683e

Author: Matthew Wilcox (Oracle) <[email protected]>
Date:   Wed Feb 9 20:21:22 2022 +0000

iomap: Fix iomap_invalidatepage tracepoint

[ Upstream commit 1241ebeca3f94b417751cb3ff62454cefdac75bc ]

This tracepoint is defined to take an offset in the file, not an offset in the folio.

fs/iomap/buffered-io.c +2 -1
index 6c51a75d0be6..d020a2e81a24 100644
@@ -480,7 +480,8 @@ EXPORT_SYMBOL_GPL(iomap_releasepage);
 
 void iomap_invalidate_folio(struct folio *folio, size_t offset, size_t len)
 {
-	trace_iomap_invalidatepage(folio->mapping->host, offset, len);
+	trace_iomap_invalidatepage(folio->mapping->host,
+					folio_pos(folio) + offset, len);
 
 	/*
 	 * If we're invalidating the entire folio, clear the dirty state