mm: unexport folio_add_lru
PATCH 1/1 mm: unexport folio_add_lru
Only used in core mm code.
--- mm/swap.c | 1 - 1 file changed, 1 deletion(-)
mm/swap.c +0 -1
@@ -459,7 +459,6 @@ void folio_add_lru(struct folio *folio)__pagevec_lru_add (pvec);local_unlock (&lru_pvecs.lock); } -EXPORT_SYMBOL (folio_add_lru);/** * lru_cache_add_inactive_or_unevictable
Signature · 1 line
2.30.2
Quoted 1 line · Christoph Hellwig
Only used in core mm code.
Yes, but that's going to be true of virtually all the folio symbols which are wrapped in folio-compat.c. Perhaps we can give this one a year to see what the CIFS and FUSE folio conversions end up looking like?
Quoted 6 lines · Matthew Wilcox
Quoted 1 line · Christoph Hellwig
Only used in core mm code.
Yes, but that's going to be true of virtually all the folio symbols which are wrapped in
folio-compat.c. Perhaps we can give this one a year to see what the CIFS and FUSE folio conversions end up looking like?
A year before exporting something random? Yes. CIFS seems to be mostly related to their strange ->readpages which shouldn't exist in this form. Fuse hs some deep mm magic related to replace_page_cache_page, which should probably deal with the LRU as well.