Re: iomap 5.15 branch construction ...

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Aug 3, 2021 at 12:11 AM Darrick J. Wong <djwong@xxxxxxxxxx> wrote:
>
> Hi everyone!
>
> iomap has become very popular for this cycle, with seemingly a lot of
> overlapping patches and whatnot.  Does this accurately reflect all the
> stuff that people are trying to send for 5.15?
>
> 1. So far, I think these v2 patches from Christoph are ready to go:
>
>         iomap: simplify iomap_readpage_actor
>         iomap: simplify iomap_add_to_ioend
>
> 2. This is the v9 "iomap: Support file tail packing" patch from Gao,
> with a rather heavily edited commit:
>
>         iomap: support reading inline data from non-zero pos
>
> Should I wait for a v10 patch with spelling fixes as requested by
> Andreas?  And if there is a v10 submission, please update the commit
> message.
>
> 3. Matthew also threw in a patch:
>
>         iomap: Support inline data with block size < page size
>
> for which Andreas also sent some suggestions, so I guess I'm waiting for
> a v2 of that patch?  It looks to me like the last time he sent that
> series (on 24 July) he incorporated Gao's patch as patch 1 of the
> series?
>
> 4. Andreas has a patch:
>
>         iomap: Fix some typos and bad grammar
>
> which looks more or less ready to go.
>
> 5. Christoph also had a series:
>
>         RFC: switch iomap to an iterator model
>
> Which I reviewed and sent some comments for, but (AFAICT) haven't seen a
> non-RFC resubmission yet.  Is that still coming for 5.15?
>
> 6. Earlier, Eric Biggers had a patchset that made some iomap changes
> ahead of porting f2fs to use directio.  I /think/ those changes were
> dropped in the latest submission because the intended use of those
> changes (counters of the number of pages undergoing reads or writes,
> iirc?) has been replaced with something simpler.  IOWs, f2fs doesn't
> need any iomap changes for 5.15, right?
>
> 7. Andreas also had a patchset:
>
>         gfs2: Fix mmap + page fault deadlocks
>
> That I've left unread because Linus started complaining about patch 1.
> Is that not going forward, then?

Still working on it; it's way nastier than expected.

> So, I /think/ that's all I've received for this next cycle.  Did I miss
> anything?  Matthew said he might roll some of these up and send me a
> pull request, which would be nice... :)
>
> --D
>

Andreas




[Index of Archives]     [XFS Filesystem Development (older mail)]     [Linux Filesystem Development]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux RAID]     [Linux SCSI]


  Powered by Linux