Re: invalidate_inode_pages in 2.5.32/3

Andrew Morton
2002-09-11T00:34:32Z

Daniel Phillips wrote:
>
> > ...
> We do get
> around to walking the ptes at file close I believe. Is that not driven by
> zap_page_range, which moves any orphaned pte dirty bits down into the struct
> page?

Nope, close will just leave all the pages pte-dirty or PageDirty in
memory. truncate will nuke all the ptes and then the pagecache.

But the normal way in which pte-dirty pages find their way to the
backing file is:

- page reclaim runs try_to_unmap or

- user runs msync(). (Which will only clean that mm's ptes!)

These will run set_page_dirty(), making the page visible to
one of the many things which run writeback.