Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 10 Sep 2002 20:56:31 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 10 Sep 2002 20:56:31 -0400 Received: from dsl-213-023-020-046.arcor-ip.net ([213.23.20.46]:11997 "EHLO starship") by vger.kernel.org with ESMTP id ; Tue, 10 Sep 2002 20:56:30 -0400 Content-Type: text/plain; charset=US-ASCII From: Daniel Phillips To: Andrew Morton Subject: Re: invalidate_inode_pages in 2.5.32/3 Date: Wed, 11 Sep 2002 02:53:58 +0200 X-Mailer: KMail [version 1.3.2] Cc: Chuck Lever , Rik van Riel , trond.myklebust@fys.uio.no, Linux Kernel Mailing List References:

<3D7E909A.512C23C1@digeo.com> In-Reply-To: <3D7E909A.512C23C1@digeo.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Message-Id: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1129 Lines: 32 On Wednesday 11 September 2002 02:38, Andrew Morton wrote: > 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. So we just quietly drop any dirty memory mapped to a file if the user doesn't run msync? Is that correct behaviour? It sure sounds wrong. -- Daniel - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/