Re: [ANNOUNCE] xfs-linux: iomap-5.4-merge rebased to 1b4fdf4f30db

["Darrick J. Wong" <darrick.wong@oracle.com>]

On Thu, Sep 19, 2019 at 10:08:04AM -0700, Christoph Hellwig wrote:
> On Thu, Sep 19, 2019 at 04:19:37PM +0000, Damien Le Moal wrote:
> > OK. Will do, but traveling this week so I will not be able to test until next week.
> 
> Which suggests zonefs won't make it for 5.4, right?  At that point
> I wonder if we should defer the whole generic iomap writeback thing
> to 5.5 entirely.  The whole idea of having two copies of the code always
> scared me, even more so given that 5.4 is slated to be a long term
> stable release.
> 
> So maybe just do the trivial typo + end_io cleanups for Linus this
> merge window?

I for one don't mind pulling back to just these three patches:

iomap: Fix trivial typo
iomap: split size and error for iomap_dio_rw ->end_io
iomap: move the iomap_dio_rw ->end_io callback into a structure

But frankly, do we even need the two directio patches?  IIRC Matthew
Bobrowski wanted them for the ext4 directio port, but seeing as Ted
isn't submitting that for 5.4 and gfs2 doesn't supply a directio endio
handler, maybe I should just send the trivial typo fix and that's it?

I hate playing into this "It's an LTS but Greg won't admit it" BS but
I'm gonna do it anyway -- for any release that's been declared to be an
LTS release, we have no business pushing new functionality (especially
if it isn't going to be used by anyone) at all.  It would have been
helpful to have had such a declaration as a solid reason to push back
against riskier additions, like I did for the last couple of LTSes.

(And since I didn't have such a tool, I was willing to push the
writeback bits anyway for the sake of zonefs since it would have been
the only user, but seeing as Linus rejected zonefs for lack of
discussion, I think that (the directio api change; iomap writeback; and
zonefs) is just going to have to wait for 5.5.)

<frustrated>

--D