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=-6.7 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS 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 1F148C636CA for ; Thu, 15 Jul 2021 22:14:55 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 044A161360 for ; Thu, 15 Jul 2021 22:14:54 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231991AbhGOWRr (ORCPT ); Thu, 15 Jul 2021 18:17:47 -0400 Received: from mail.kernel.org ([198.145.29.99]:52346 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231547AbhGOWRq (ORCPT ); Thu, 15 Jul 2021 18:17:46 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id A3BDD61278; Thu, 15 Jul 2021 22:14:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1626387292; bh=SgJELlTSAdq220KSsy6qE+TbsJwWUUb96DSopClSFYM=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Vnk5/oYWXUI/6cpJAgYt98kt4SzyXbJMneQjY2ew/BfFVdkPChfq84AFBxhUxztLa LmnXMGZuEGWvOv01yIXMoquwTWXbZDFFNgRvHj95kM33/Hp39hHzAtxDSCmCY/m9vx 1Y9YslFNvIRzyBUgGlEziqb4mjcsck7HgPDO3GUr/inpugLYG6yA4vhHskDytv2BCL N5gMO/1m98G79oyynsT9xNb8BuhO3Gb8qj3RxV5DKwgdCKhNX4PhezbxzAEgG6tPpv Dppsi59MqDp8PGiR1JO9uBSWaqWApKfwDWh4XBZHvPDVlLr0NBb1h65PPoFZZgMo7E /itUmX6ILFy/A== Date: Thu, 15 Jul 2021 15:14:52 -0700 From: "Darrick J. Wong" To: Christoph Hellwig Cc: Rafa?? Mi??ecki , Greg KH , Al Viro , Linus Torvalds , Konstantin Komarov , Hans de Goede , linux-fsdevel , LKML Subject: Re: [GIT PULL] vboxsf fixes for 5.14-1 Message-ID: <20210715221452.GV22357@magnolia> References: <30c7ec73-4ad5-3c4e-4745-061eb22f2c8a@redhat.com> <7f4a96bc-3912-dfb6-4a32-f0c6487d977b@gmail.com> <20210714161352.GA22357@magnolia> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 14, 2021 at 05:18:07PM +0100, Christoph Hellwig wrote: > On Wed, Jul 14, 2021 at 09:13:52AM -0700, Darrick J. Wong wrote: > > Porting to fs/iomap can be done after merge, so long as the ntfs3 > > driver doesn't depend on crazy reworking of buffer heads or whatever. > > AFAICT it didn't, so ... yes, my earlier statements still apply: "later > > as a clean up". > > I on the other hand hate piling up mor of this legacy stuff, as it tends > to not be cleaned up by the submitted. Example: erofs still hasn't > switched to iomap despite broad claims, I was letting that one go while willy tries to land all the folio surgery on the iomap code. > also we still have a huge backlog in the switch to the new mount API. That's true, though having /read/ the xfs conversion series, I'm not surprised that most maintainers don't want to do the heavy lift themselves. --D