[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210715221452.GV22357@magnolia>
Date: Thu, 15 Jul 2021 15:14:52 -0700
From: "Darrick J. Wong" <djwong@...nel.org>
To: Christoph Hellwig <hch@...radead.org>
Cc: Rafa?? Mi??ecki <zajec5@...il.com>,
Greg KH <gregkh@...uxfoundation.org>,
Al Viro <viro@...iv.linux.org.uk>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Konstantin Komarov <almaz.alexandrovich@...agon-software.com>,
Hans de Goede <hdegoede@...hat.com>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] vboxsf fixes for 5.14-1
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,
<shrug> 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
Powered by blists - more mailing lists