On Tue, May 19, 2020 at 03:11:16PM -0500, Goldwyn Rodrigues wrote: > On 7:13 15/05, Christoph Hellwig wrote: > > FYI, generic/475 always fail on me for btrfs, due to the warnings on > > transaction abort. > > > > Anyway, I have come up with a version that seems to mostly work. > > > > The main change is that btrfs_sync_file stashes away the journal handle. > > I also had to merge parts of the ->iomap_end patch into the main iomap > > one. I also did some cleanups to my iomap changes while looking over it. > > Let me know what you thing, the tree is here: > > > > git://git.infradead.org/users/hch/misc.git btrfs-dio > > > > Gitweb: > > > > http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/btrfs-dio > > I finally managed to fix the reservation issue and the final tree based > on Dave's for-next is at: > https://github.com/goldwynr/linux/tree/dio-merge > > I will test it thoroughly and send another patchset. > I will still need that iomap->private! With the updated top commit 6cbb7a0c7b33d33e6 it passes fstests in my setup, so that's the minimum for inclusion. Regarding merge, I'm willing to add it to 5.8 queue still. In total it's 7 patches, 6 of which are preparatory or cleanups that have been reviewed by several people. The switch to iomap is one patch and not a huge one. Sending the latest version proably makes sense so we have it in the mailinglist, I can add the patches to misc-next right away so it gets more testing exposure. There have been other changes to our direct IO code so the testing focus will be there anyway and reverting one or two patches as fallback is an option, I think the risk of including the patches that close to merge window is manageable.
