From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from verein.lst.de ([213.95.11.211]:40225 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751162AbdJYGTa (ORCPT ); Wed, 25 Oct 2017 02:19:30 -0400 Date: Wed, 25 Oct 2017 08:19:29 +0200 From: Christoph Hellwig Subject: Re: [PATCH 2/4] xfs: remove xfs_bmbt_validate_extent Message-ID: <20171025061929.GA4601@lst.de> References: <20171023063017.11520-1-hch@lst.de> <20171023063017.11520-3-hch@lst.de> <20171023154119.GC5483@magnolia> <20171024075415.GA14823@lst.de> <20171025052426.GB20669@magnolia> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171025052426.GB20669@magnolia> Sender: linux-xfs-owner@vger.kernel.org List-ID: List-Id: xfs To: "Darrick J. Wong" Cc: Christoph Hellwig , linux-xfs@vger.kernel.org On Tue, Oct 24, 2017 at 10:24:26PM -0700, Darrick J. Wong wrote: > On Tue, Oct 24, 2017 at 09:54:15AM +0200, Christoph Hellwig wrote: > > > By removing this, I think we no longer report corruption if we encounter > > > 'unwritten' attr fork extents, which (AFAIK) aren't allowed. > > > > True. Oh well, skip this patch for now if you apply the rest, and > > I'll have to do some gymnastics to keep it. > > Ok. I can try to fix it up in the patch stack tomorrow, but feel free > to beat me to it. :P Just discard all the patches but the first for now.