mm-vmscan-remove-folio_test_private-check-in-pageout-fix

redo comment, per David

Link: https://lkml.kernel.org/r/17d1b293-e393-4989-a357-7eea74b3c805@redhat.com
Cc: Baolin Wang <baolin.wang@linux.alibaba.com>
Cc: David Hildenbrand <david@redhat.com>
Cc: Hugh Dickins <hughd@google.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>
Cc: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
Cc: Michal Hocko <mhocko@kernel.org>
Cc: Qi Zheng <zhengqi.arch@bytedance.com>
Cc: Shakeel Butt <shakeel.butt@linux.dev>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>

diff --git a/mm/vmscan.c b/mm/vmscan.c
index 784d14d27a05256d0b75d661177dc0d265de0fb1..75225a54d5b159971d32e2ade838428a9032eff1 100644 (file)
--- a/mm/vmscan.c
+++ b/mm/vmscan.c
@@ -701,8 +701,8 @@ static pageout_t pageout(struct folio *folio, struct address_space *mapping,
                return PAGE_KEEP;
        if (!mapping) {
                /*
-                * Is it still possible to have a dirty folio with
-                * a NULL mapping? I think not.
+                * We should no longer have dirty folios with clean buffers and
+                * a NULL mapping. However, let's be careful for now.
                 */
                VM_WARN_ON_FOLIO(true, folio);
                return PAGE_KEEP;