On 16/10/2024 11:03, John Garry wrote:
Hi Jens,
There are block changes in this series. I was going to ask Carlos to
queue this work via the XFS tree, so can you let me know whether you
have any issue with those (block) changes. There is a fix included,
which I can manually backport to stable (if not autoselected).
Note that I still plan on sending a v10 for this series, to fix a small
documentation issue which Darrick noticed.
BTW, I was hoping to send non-RFCs patches for atomic write RAID support
soon, originally sent in:
https://lore.kernel.org/linux-block/20240919092302.3094725-1-john.g.garry@xxxxxxxxxx/
https://lore.kernel.org/linux-block/20240903150748.2179966-1-john.g.garry@xxxxxxxxxx/
They should not have any dependency or conflict with this series.
Thanks,
John
This series expands atomic write support to filesystems, specifically
XFS.
Initially we will only support writing exactly 1x FS block atomically.
Since we can now have FS block size > PAGE_SIZE for XFS, we can write
atomically 4K+ blocks on x86.
...
John Garry (8):
block/fs: Pass an iocb to generic_atomic_write_valid()
fs/block: Check for IOCB_DIRECT in generic_atomic_write_valid()
block: Add bdev atomic write limits helpers
fs: Export generic_atomic_write_valid()
fs: iomap: Atomic write support
xfs: Support atomic write for statx
xfs: Validate atomic writes
xfs: Support setting FMODE_CAN_ATOMIC_WRITE
.../filesystems/iomap/operations.rst | 11 ++++++
block/fops.c | 22 ++++++-----
fs/iomap/direct-io.c | 38 +++++++++++++++++--
fs/iomap/trace.h | 3 +-
fs/read_write.c | 16 +++++---
fs/xfs/xfs_buf.c | 7 ++++
fs/xfs/xfs_buf.h | 4 ++
fs/xfs/xfs_file.c | 16 ++++++++
fs/xfs/xfs_inode.h | 15 ++++++++
fs/xfs/xfs_iops.c | 22 +++++++++++
include/linux/blkdev.h | 16 ++++++++
include/linux/fs.h | 2 +-
include/linux/iomap.h | 1 +
13 files changed, 151 insertions(+), 22 deletions(-)
