xfs: Remove mention of PageWriteback

Update a comment to refer to folios instead of pages.

Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Carlos Maiolino <cem@kernel.org>

diff --git a/fs/xfs/xfs_reflink.c b/fs/xfs/xfs_reflink.c
index db23a0f231d67b8adae43dfae45f46ca2a4a1d08..251dec48f0e381edfa78d7db626a644a20b489df 100644 (file)
--- a/fs/xfs/xfs_reflink.c
+++ b/fs/xfs/xfs_reflink.c
@@ -949,16 +949,16 @@ xfs_reflink_end_cow(
         * repeatedly cycles the ILOCK to allocate one transaction per remapped
         * extent.
         *
-        * If we're being called by writeback then the pages will still
-        * have PageWriteback set, which prevents races with reflink remapping
-        * and truncate.  Reflink remapping prevents races with writeback by
-        * taking the iolock and mmaplock before flushing the pages and
-        * remapping, which means there won't be any further writeback or page
-        * cache dirtying until the reflink completes.
+        * If we're being called by writeback then the folios will still
+        * have the writeback flag set, which prevents races with reflink
+        * remapping and truncate.  Reflink remapping prevents races with
+        * writeback by taking the iolock and mmaplock before flushing
+        * the folios and remapping, which means there won't be any further
+        * writeback or page cache dirtying until the reflink completes.
         *
         * We should never have two threads issuing writeback for the same file
         * region.  There are also have post-eof checks in the writeback
-        * preparation code so that we don't bother writing out pages that are
+        * preparation code so that we don't bother writing out folios that are
         * about to be truncated.
         *
         * If we're being called as part of directio write completion, the dio