Commit 60d82310 authored by Matthew Wilcox (Oracle)'s avatar Matthew Wilcox (Oracle)
Browse files

iomap: Support large folios in invalidatepage 



If we're punching a hole in a large folio, we need to remove the
per-folio iomap data as the folio is about to be split and each page will
need its own.  If a dirty folio is only partially-uptodate, the iomap
data contains the information about which blocks cannot be written back,
so assert that a dirty folio is fully uptodate.

Signed-off-by: default avatarMatthew Wilcox (Oracle) <willy@infradead.org>
Reviewed-by: default avatarChristoph Hellwig <hch@lst.de>
Reviewed-by: default avatarDarrick J. Wong <djwong@kernel.org>
parent 589110e8

fs/iomap/buffered-io.c

+7 −2
Original line number Diff line number Diff line
@@ -481,13 +481,18 @@ void iomap_invalidate_folio(struct folio *folio, size_t offset, size_t len) 
	trace_iomap_invalidatepage(folio->mapping->host, offset, len);



	/*

	 * If we're invalidating the entire page, clear the dirty state from it

	 * and release it to avoid unnecessary buildup of the LRU.

	 * If we're invalidating the entire folio, clear the dirty state

	 * from it and release it to avoid unnecessary buildup of the LRU.

	 */

	if (offset == 0 && len == folio_size(folio)) {

		WARN_ON_ONCE(folio_test_writeback(folio));

		folio_cancel_dirty(folio);

		iomap_page_release(folio);

	} else if (folio_test_large(folio)) {

		/* Must release the iop so the page can be split */

		WARN_ON_ONCE(!folio_test_uptodate(folio) &&

			     folio_test_dirty(folio));

		iomap_page_release(folio);

	}

}

EXPORT_SYMBOL_GPL(iomap_invalidate_folio);