Re: [RFC PATCH 3/3] mm: Split page_has_private() in two to better handle PG_private_2

On Fri, Apr 09, 2021 at 11:59:29AM +0100, David Howells wrote: > diff --git a/fs/iomap/buffered-io.c b/fs/iomap/buffered-io.c > index 414769a6ad11..9c89db033548 100644 > --- a/fs/iomap/buffered-io.c > +++ b/fs/iomap/buffered-io.c > @@ -41,7 +41,7 @@ static inline struct iomap_page *to_iomap_page(st

[RFC PATCH 3/3] mm: Split page_has_private() in two to better handle PG_private_2

Split page_has_private() into two functions: (1) page_needs_cleanup() to find out if a page needs the ->releasepage(), ->invalidatepage(), etc. address space ops calling upon it. This returns true when either PG_private or PG_private_2 are set. (2) page_private_count() which returns