From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 9 May 2001 22:10:50 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 9 May 2001 22:10:30 -0400 Received: from horus.its.uow.edu.au ([130.130.68.25]:45050 "EHLO horus.its.uow.edu.au") by vger.kernel.org with ESMTP id ; Wed, 9 May 2001 22:10:28 -0400 Message-ID: <3AF9F7F2.AC47F7AC@uow.edu.au> Date: Thu, 10 May 2001 12:07:46 +1000 From: Andrew Morton X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.3-ac13 i686) X-Accept-Language: en MIME-Version: 1.0 To: Marcelo Tosatti CC: Linus Torvalds , "David S. Miller" , lkml Subject: Re: [PATCH] writepage method changes In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Marcelo Tosatti wrote: > > Well, > > Here is the updated version of the patch to add the "priority" argument to > writepage(). It appears that a -EIO return from block_write_full_page() will result in an unlock of an unlocked page in page_launder(). Splat. What does the new writepage() argument do, and why does it exist? What action should the individual writepage()s take in response to different values of `priority'? What is the meaning of the writepage return value for the respective values of `priority'? When should writepage return with the page locked, and when not? -