This patchset does not work. It will eat your filesystem. Do not apply.
The bug starts to show up with the fourth patch ("Convert direct_IO write
support to use iomap"). generic/013 creates a corrupt filesystem and
fsck fails to fix it, which shows all kinds of fun places in xfstests
where we neglect to check that 'mount' actually mounted the filesystem.
set -x or die.
I'm hoping one of the people who knows iomap better than I do can just
point at the bug and say "Duh, it doesn't work like that".
It's safe to say that every patch after patch 6 is untested. I'm not
convinced that I really tested patch 6 either.
Matthew Wilcox (Oracle) (9):
IOMAP_DIO_NOSYNC
jfs: Add jfs_iomap_begin()
jfs: Convert direct_IO read support to use iomap
jfs: Convert direct_IO write support to use iomap
jfs: Remove old direct_IO support
jfs: Handle bmap with iomap
jfs: Read quota through the page cache
jfs: Write quota through the page cache
jfs: Convert buffered IO paths to iomap
fs/iomap/direct-io.c | 3 +-
fs/jfs/file.c | 56 +++++++++++++++++-
fs/jfs/inode.c | 128 ++++++++++++++++--------------------------
fs/jfs/jfs_inode.h | 2 +-
fs/jfs/jfs_logmgr.c | 1 -
fs/jfs/jfs_metapage.c | 1 -
fs/jfs/super.c | 127 +++++++++++++++++++----------------------
include/linux/iomap.h | 6 ++
8 files changed, 168 insertions(+), 156 deletions(-)
--
2.34.1
