From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail202.messagelabs.com (mail202.messagelabs.com [216.82.254.227]) by kanga.kvack.org (Postfix) with ESMTP id 169906B009B for ; Tue, 3 Mar 2009 09:26:13 -0500 (EST) Subject: Re: [rfc][patch 2/2] buffer, btrfs: fix page_mkwrite error cases From: Chris Mason In-Reply-To: <20090303104114.GD17042@wotan.suse.de> References: <20090303103838.GC17042@wotan.suse.de> <20090303104114.GD17042@wotan.suse.de> Content-Type: text/plain Date: Tue, 03 Mar 2009 09:26:03 -0500 Message-Id: <1236090363.782.6.camel@think.oraclecorp.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org To: Nick Piggin Cc: Linux Memory Management List , linux-fsdevel@vger.kernel.org List-ID: On Tue, 2009-03-03 at 11:41 +0100, Nick Piggin wrote: > page_mkwrite is called with neither the page lock nor the ptl held. This > means a page can be concurrently truncated or invalidated out from underneath > it. Callers are supposed to prevent truncate races themselves, however > previously the only thing they can do in case they hit one is to raise a > SIGBUS. A sigbus is wrong for the case that the page has been invalidated > or truncated within i_size (eg. hole punched). Callers may also have to > perform memory allocations in this path, where again, SIGBUS would be wrong. > > The previous patch made it possible to properly specify errors. Convert > the generic buffer.c code and btrfs to return sane error values > (in the case of page removed from pagecache, VM_FAULT_NOPAGE will cause the > fault handler to exit without doing anything, and the fault will be retried > properly). > Thanks Nick. I think the btrfs patch needs an extra } to compile, but it looks fine. -chris -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org