From: John Garry <john.g.garry@oracle.com>
To: axboe@kernel.dk, cem@kernel.org
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
hare@suse.de, martin.petersen@oracle.com,
catherine.hoang@oracle.com, mcgrof@kernel.org,
ritesh.list@gmail.com, ojaswin@linux.ibm.com, brauner@kernel.org,
djwong@kernel.org, viro@zeniv.linux.org.uk, jack@suse.cz,
dchinner@redhat.com, hch@lst.de
Subject: Re: [PATCH v9 0/8] block atomic writes for xfs
Date: Fri, 18 Oct 2024 10:29:17 +0100 [thread overview]
Message-ID: <8107c05d-1222-4e47-bbcd-eba64e085669@oracle.com> (raw)
In-Reply-To: <20241016100325.3534494-1-john.g.garry@oracle.com>
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@oracle.com/
https://lore.kernel.org/linux-block/20240903150748.2179966-1-john.g.garry@oracle.com/
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(-)
>
next prev parent reply other threads:[~2024-10-18 9:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 10:03 [PATCH v9 0/8] block atomic writes for xfs John Garry
2024-10-16 10:03 ` [PATCH v9 1/8] block/fs: Pass an iocb to generic_atomic_write_valid() John Garry
2024-10-16 10:03 ` [PATCH v9 2/8] fs/block: Check for IOCB_DIRECT in generic_atomic_write_valid() John Garry
2024-10-16 19:57 ` Darrick J. Wong
2024-10-16 10:03 ` [PATCH v9 3/8] block: Add bdev atomic write limits helpers John Garry
2024-10-16 12:29 ` Christoph Hellwig
2024-10-16 12:36 ` John Garry
2024-10-16 12:39 ` Christoph Hellwig
2024-10-16 19:58 ` Darrick J. Wong
2024-10-16 10:03 ` [PATCH v9 4/8] fs: Export generic_atomic_write_valid() John Garry
2024-10-16 10:03 ` [PATCH v9 5/8] fs: iomap: Atomic write support John Garry
2024-10-16 20:03 ` Darrick J. Wong
2024-10-17 7:57 ` John Garry
2024-10-16 10:03 ` [PATCH v9 6/8] xfs: Support atomic write for statx John Garry
2024-10-16 10:03 ` [PATCH v9 7/8] xfs: Validate atomic writes John Garry
2024-10-16 12:29 ` Christoph Hellwig
2024-10-16 20:13 ` Darrick J. Wong
2024-10-16 10:03 ` [PATCH v9 8/8] xfs: Support setting FMODE_CAN_ATOMIC_WRITE John Garry
2024-10-16 20:13 ` Darrick J. Wong
2024-10-18 9:29 ` John Garry [this message]
2024-10-18 13:41 ` [PATCH v9 0/8] block atomic writes for xfs Jens Axboe
2024-10-18 17:43 ` John Garry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8107c05d-1222-4e47-bbcd-eba64e085669@oracle.com \
--to=john.g.garry@oracle.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=catherine.hoang@oracle.com \
--cc=cem@kernel.org \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mcgrof@kernel.org \
--cc=ojaswin@linux.ibm.com \
--cc=ritesh.list@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox