mm/writeback: update filemap_dirty_folio() comment

inevity · opsiff · commit a3a0e6d14f7c · 2026-04-10T10:38:31.000+08:00
mainline inclusion from mainline-v6.7-rc1 category: other Change to use new address space operation dirty_folio(). Link: https://lkml.kernel.org/r/20230917-trycontrib1-v1-1-db22630b8839@gmail.com Fixes: 6f31a5a ("fs: Add aops->dirty_folio") Signed-off-by: Jianguo Bau <roidinev@gmail.com> Cc: Matthew Wilcox (Oracle) <willy@infradead.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> (cherry picked from commit ab428b4) Signed-off-by: Wentao Guan <guanwentao@uniontech.com>
diff --git a/mm/page-writeback.c b/mm/page-writeback.c
@@ -2734,7 +2734,7 @@ void __folio_mark_dirty(struct folio *folio, struct address_space *mapping,
  * @folio: Folio to be marked as dirty.
  *
  * Filesystems which do not use buffer heads should call this function
- * from their set_page_dirty address space operation.  It ignores the
+ * from their dirty_folio address space operation.  It ignores the
  * contents of folio_get_private(), so if the filesystem marks individual
  * blocks as dirty, the filesystem should handle that itself.
  *

Original file line number	Diff line number	Diff line change
`@@ -2734,7 +2734,7 @@ void __folio_mark_dirty(struct folio folio, struct address_space mapping,`
`2734`	`2734`	`* @folio: Folio to be marked as dirty.`
`2735`	`2735`	`*`
`2736`	`2736`	`* Filesystems which do not use buffer heads should call this function`
`2737`		`- * from their set_page_dirty address space operation. It ignores the`
	`2737`	`+ * from their dirty_folio address space operation. It ignores the`
`2738`	`2738`	`* contents of folio_get_private(), so if the filesystem marks individual`
`2739`	`2739`	`* blocks as dirty, the filesystem should handle that itself.`
`2740`	`2740`	`*`