From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 128AA3DEAD3; Thu, 18 Jun 2026 08:58:01 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.137.202.133 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781773091; cv=none; b=TmO7Ca7Gi1O+Sf5/dqufAsa8SGtj2hhmVSnnDZtMdIRTx9xr9Nb/enrOvsOMaIuhBso07xkb24vfXf/uKYPgYiLmyK18V9Dj9/yxskdvl4TO3sMcYYIRDAl8hUZqqXc2BY44F+coVTX/Q2gI/k3bRJQYPCNGyUnInt8cN9pblRY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781773091; c=relaxed/simple; bh=DRS/FIfLaujjZj+AsiPwk4bvPyKbGEHdXqHDoQoFnb0=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=Nwe842gwDE9BMpFJ8ZspGKOMfOVRVaBQXAgspjvmq/8B4+DEVceo+/7J6lPoTeDR2p41Rtj6NZpCtddVVuaf8ZSNZLs/y0TbVQvXEtxiYg7WAWlrIGBmkIzvgqG/gsC5ITCmJB3xi8gubbe+9oEx969y6suSAX6qxYj34Nbb7HM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=infradead.org; spf=none smtp.mailfrom=bombadil.srs.infradead.org; dkim=pass (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b=psl6gWoZ; arc=none smtp.client-ip=198.137.202.133 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=infradead.org Authentication-Results: smtp.subspace.kernel.org; spf=none smtp.mailfrom=bombadil.srs.infradead.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b="psl6gWoZ" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20210309; h=In-Reply-To:Content-Type:MIME-Version :References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=Di6uLJ59HEcO8cD37aP1XkFmRVYxWa5zWHj0HviWVp8=; b=psl6gWoZQ+MLUwF1vxNInomZnE onuVwGSzwPWKt+Gx95D4Vp6prqrShTHXp4XERuYckjkUUGVsOxVsXvw5jOYeR6a16/Xyj5mJ8YFNS iurh4EZlDUhO3fCz3ujCxj8WXcuIWcNV2+fPioqn5oMR9uNdgu3Q/HlvAp7k0r3FTP6lxcwHpBP1O rBY84QG+WO84qAGfcr8tR43wkj7EAxS1PpVc7C2pSqkyvnL/NRobGtYGLoek07ujkCCXWdgeyTLbl QnPKzRt4hKTMbB5AE3Dsoai3WQq77r7whQRImM9JbtU8lqSVYWb25Mpd5Ndftnz9wfwO0gokN7K1f s9AUNm8A==; Received: from hch by bombadil.infradead.org with local (Exim 4.99.1 #2 (Red Hat Linux)) id 1wa8ZQ-00000000t3e-1ByC; Thu, 18 Jun 2026 08:57:56 +0000 Date: Thu, 18 Jun 2026 01:57:56 -0700 From: Christoph Hellwig To: "Pankaj Raghav (Samsung)" Cc: Zhang Yi , Pankaj Raghav , linux-xfs@vger.kernel.org, bfoster@redhat.com, lukas@herbolt.com, "Darrick J . Wong" , dgc@kernel.org, gost.dev@samsung.com, andres@anarazel.de, kundan.kumar@samsung.com, cem@kernel.org, linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org Subject: Re: [PATCH v6 3/3] xfs: add support for FALLOC_FL_WRITE_ZEROES Message-ID: References: <20260611114029.176200-4-p.raghav@samsung.com> <557b2e5c-7c65-48de-87a9-6fba21eca99f@huaweicloud.com> <6l3n2w2b7qoz2g3kfu3xsdjhlzq6m4ocs6ptq2esq27wxrb5ve@5gqv4ei4gi4b> Precedence: bulk X-Mailing-List: linux-api@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6l3n2w2b7qoz2g3kfu3xsdjhlzq6m4ocs6ptq2esq27wxrb5ve@5gqv4ei4gi4b> X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.infradead.org. See http://www.infradead.org/rpr.html On Thu, Jun 18, 2026 at 10:18:49AM +0200, Pankaj Raghav (Samsung) wrote: > So, I could do xfs_zero_range(offset, offset_ru)[1] and xfs_zero_range(end_rd, end). > (offset_ru, end_rd) will be using the accelerated XFS_BMAPI_ZERO to > zero out the extents. Yeah. > I also need to add pagecache_isize_extended and filemap_write_and_wait_range > to persist the xfs_zero_range calls before we call setfilesize. Yeah, Or we need to find a way to use xfs_falloc_setsize after all which would share all that code, although I'm not really sure how that would work best.