From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id ACE61C47404 for ; Mon, 14 Oct 2019 07:18:31 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 8BB0220882 for ; Mon, 14 Oct 2019 07:18:31 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730109AbfJNHSa (ORCPT ); Mon, 14 Oct 2019 03:18:30 -0400 Received: from verein.lst.de ([213.95.11.211]:47575 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729928AbfJNHSa (ORCPT ); Mon, 14 Oct 2019 03:18:30 -0400 Received: by verein.lst.de (Postfix, from userid 2407) id B40E768CFC; Mon, 14 Oct 2019 09:18:27 +0200 (CEST) Date: Mon, 14 Oct 2019 09:18:27 +0200 From: Christoph Hellwig To: "Darrick J. Wong" Cc: Christoph Hellwig , linux-xfs@vger.kernel.org Subject: Re: [PATCH 1/2] xfs: disable xfs_ioc_space for always COW inodes Message-ID: <20191014071827.GD10081@lst.de> References: <20191011130316.13373-1-hch@lst.de> <20191011130316.13373-2-hch@lst.de> <20191012002954.GM13108@magnolia> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191012002954.GM13108@magnolia> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-xfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-xfs@vger.kernel.org On Fri, Oct 11, 2019 at 05:29:54PM -0700, Darrick J. Wong wrote: > On Fri, Oct 11, 2019 at 03:03:15PM +0200, Christoph Hellwig wrote: > > If we always have to write out of place preallocating blocks is > > pointless. We already check for this in the normal falloc path, but > > the check was missig in the legacy ALLOCSP path. > > This function handles other things than preallocation, such as > XFS_IOC_ZERO_RANGE and XFS_IOC_UNRESVSP, which call xfs_zero_file_space > and xfs_free_file_space, respectively. We don't prohibit fallocate > from calling those two functions on an always_cow inode, so why do that > here? True. I actually have a patch in my tree that switches those to be handled in the core so that they enter XFS through ->fallocate. It didn't make any sense to send this patch before that other change, sorry.