Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756228AbZFCJgd (ORCPT ); Wed, 3 Jun 2009 05:36:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756644AbZFCJfr (ORCPT ); Wed, 3 Jun 2009 05:35:47 -0400 Received: from cantor.suse.de ([195.135.220.2]:46784 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756689AbZFCJfq (ORCPT ); Wed, 3 Jun 2009 05:35:46 -0400 Date: Wed, 3 Jun 2009 11:35:46 +0200 From: Nick Piggin To: Andi Kleen Cc: Wu Fengguang , "hugh@veritas.com" , "riel@redhat.com" , "akpm@linux-foundation.org" , "chris.mason@oracle.com" , "linux-kernel@vger.kernel.org" , "linux-mm@kvack.org" Subject: Re: [PATCH] [13/16] HWPOISON: The high level memory error handler in the VM v3 Message-ID: <20090603093546.GA16275@wotan.suse.de> References: <20090528122357.GM6920@wotan.suse.de> <20090528135428.GB16528@localhost> <20090601115046.GE5018@wotan.suse.de> <20090601183225.GS1065@one.firstfloor.org> <20090602120042.GB1392@wotan.suse.de> <20090602124757.GG1065@one.firstfloor.org> <20090602125713.GG1392@wotan.suse.de> <20090602134659.GA21338@localhost> <20090602151729.GC17448@wotan.suse.de> <20090602172715.GT1065@one.firstfloor.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090602172715.GT1065@one.firstfloor.org> User-Agent: Mutt/1.5.9i Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1119 Lines: 29 On Tue, Jun 02, 2009 at 07:27:15PM +0200, Andi Kleen wrote: > > Hmm, if you're handling buffercache here then possibly yes. > > Good question, will check. BTW. now that I think about it, buffercache is probably not a good idea to truncate (truncate, as-in: remove from pagecache). Because filesystems can assume that with just a reference on the page, then it will not be truncated. This code will cause ext2 (as the first one I looked at), to go oops. And this is not predicated on PagePrivate or page_has_buffers, because filesystems are free to directly operate on their own metadata buffercache pages. So I think it would be a good idea to exclude buffercache from here completely until it can be shown to be safe. Actually you *can* use the invalidate_mapping_pages path, which will check refcounts etc (or a derivative thereof, similarly to my truncate patch). -- 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/