From mboxrd@z Thu Jan 1 00:00:00 1970 From: Martin Jambor Subject: Writing out a (file) mmapped page Date: Sun, 12 Jun 2005 18:49:24 +0200 Message-ID: <8e70aacf050612094916d32276@mail.gmail.com> Reply-To: Martin Jambor Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Return-path: Received: from zproxy.gmail.com ([64.233.162.200]:27879 "EHLO zproxy.gmail.com") by vger.kernel.org with ESMTP id S262643AbVFLQta convert rfc822-to-8bit (ORCPT ); Sun, 12 Jun 2005 12:49:30 -0400 Received: by zproxy.gmail.com with SMTP id 9so1360509nzo for ; Sun, 12 Jun 2005 09:49:24 -0700 (PDT) To: linux-fsdevel@vger.kernel.org Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Hi, I have spent a few hours trying to find out how dirty mmapped pages are written out in filesystems using the "generic" functions but so far I have not been successful. The main thing that escapes me is the following: block_write_full_page() writes out only buffers marked dirty or whole page when there are no buffers associated with it. Where in kernel are buffers either marked dirty or stripped off a mmaped page when the page itself becomes dirty? I would be very grateful for a pointer to the source, possibly accompanied by a brief explanation of how it gets called. One comment in buffer.c suggests aops->prepare_write is called by a pagefault handler for mmaped pages but I found no such call (using cscope). Thank you very much for any comment on this, Martin Jambor