From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Zijlstra Subject: Re: [patch][rfc] mm: hold page lock over page_mkwrite Date: Thu, 26 Feb 2009 10:20:18 +0100 Message-ID: <1235640018.4645.4692.camel@laptop> References: <20090225093629.GD22785@wotan.suse.de> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org, Linux Memory Management List To: Nick Piggin Return-path: Received: from casper.infradead.org ([85.118.1.10]:58474 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751368AbZBZJUZ (ORCPT ); Thu, 26 Feb 2009 04:20:25 -0500 In-Reply-To: <20090225093629.GD22785@wotan.suse.de> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Wed, 2009-02-25 at 10:36 +0100, Nick Piggin wrote: > + if (!page_mkwrite) > + wait_on_page_locked(dirty_page); > set_page_dirty_balance(dirty_page, page_mkwrite); > put_page(dirty_page); > + if (page_mkwrite) { > + unlock_page(old_page); > + page_cache_release(old_page); > + } We're calling into the whole balance_dirty_pages() writeout path with a page locked.. is that sensible?