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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id ABE79C433F5 for ; Mon, 25 Apr 2022 11:09:48 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241651AbiDYLMt (ORCPT ); Mon, 25 Apr 2022 07:12:49 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35626 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S241710AbiDYLMg (ORCPT ); Mon, 25 Apr 2022 07:12:36 -0400 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9ECA012A94 for ; Mon, 25 Apr 2022 04:09:31 -0700 (PDT) Received: by verein.lst.de (Postfix, from userid 2407) id 79C0F68AFE; Mon, 25 Apr 2022 13:09:28 +0200 (CEST) Date: Mon, 25 Apr 2022 13:09:28 +0200 From: Christoph Hellwig To: Qu Wenruo Cc: Christoph Hellwig , Josef Bacik , David Sterba , Qu Wenruo , Naohiro Aota , linux-btrfs@vger.kernel.org Subject: Re: [PATCH 03/10] btrfs: split btrfs_submit_data_bio Message-ID: <20220425110928.GA24430@lst.de> References: <20220425075418.2192130-1-hch@lst.de> <20220425075418.2192130-4-hch@lst.de> <62f71a43-8167-f29f-8e9f-d95bc6667e0e@gmx.com> <20220425091920.GC16446@lst.de> <458ba4e0-15f3-93e4-bc17-ae464bdf13e7@gmx.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <458ba4e0-15f3-93e4-bc17-ae464bdf13e7@gmx.com> User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org On Mon, Apr 25, 2022 at 05:37:40PM +0800, Qu Wenruo wrote: > Oh, please don't completely get rid of btrfs_bio, even just for writes. > > The btrfs_bio::iter is pretty important for us to grab the original > logical bytenr of a bio. > As bio::bi_iter can be modified by lower level (does dm modifies it > too?), or btrfs itself. > > In fact, my incoming updated btrfs repair repair code heavily rely on > btrfs_bio::iter, both read and write, to grab the original logical > bytenr of the bio. Then it's doing the wrong thing. I actually have a series to remove it entirely.