From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: with ECARTIS (v1.0.0; list xfs); Tue, 15 Jul 2008 05:21:51 -0700 (PDT) Received: from cuda.sgi.com (cuda1.sgi.com [192.48.168.28]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id m6FCLk2f000833 for ; Tue, 15 Jul 2008 05:21:46 -0700 Date: Tue, 15 Jul 2008 08:22:50 -0400 From: Christoph Hellwig Subject: Re: xfs bug in 2.6.26-rc9 Message-ID: <20080715122250.GA15744@infradead.org> References: <487B019B.9090401@sgi.com> <20080714121332.GX29319@disturbed> <200807151617.58329.nickpiggin@yahoo.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200807151617.58329.nickpiggin@yahoo.com.au> Sender: xfs-bounce@oss.sgi.com Errors-to: xfs-bounce@oss.sgi.com List-Id: xfs To: Nick Piggin Cc: Dave Chinner , Lachlan McIlroy , Mikael Abrahamsson , linux-kernel@vger.kernel.org, xfs@oss.sgi.com, linux-mm@kvack.org > It would be easily possible to do, yes. What happened to your plans to merge ->nopfn into ->fault? Beeing able to restart page based faults would be a logical fallout from that.