public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: John Garry <john.g.garry@oracle.com>
To: Jens Axboe <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, hch@lst.de,
	brauner@kernel.org, djwong@kernel.org, viro@zeniv.linux.org.uk,
	jack@suse.cz, dchinner@redhat.com
Subject: Re: (subset) [PATCH v10 0/8] block atomic writes for xfs
Date: Wed, 23 Oct 2024 13:42:24 +0100	[thread overview]
Message-ID: <e8a3a228-0367-43da-8cad-caaaa207f0e6@oracle.com> (raw)
In-Reply-To: <d6d920c6-9a8c-49b7-8d4a-fbeacd6906f0@kernel.dk>

On 19/10/2024 23:50, Jens Axboe wrote:
>> On Sat, 19 Oct 2024 12:51:05 +0000, John Garry wrote:
>>> 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.
>>>
>>> [...]
>> Applied, thanks!
>>
>> [1/8] block/fs: Pass an iocb to generic_atomic_write_valid()
>>        commit: 9a8dbdadae509e5717ff6e5aa572ca0974d2101d
>> [2/8] fs/block: Check for IOCB_DIRECT in generic_atomic_write_valid()
>>        commit: c3be7ebbbce5201e151f17e28a6c807602f369c9
>> [3/8] block: Add bdev atomic write limits helpers
>>        commit: 1eadb157947163ca72ba8963b915fdc099ce6cca

Thanks Jens

> These are now sitting in:
> 
> git://git.kernel.dk/linux for-6.13/block-atomic
> 
> and can be pulled in by the fs/xfs people.

Carlos, can you kindly consider merging that branch and picking up the 
iomap + xfs changes?

Cheers


  reply	other threads:[~2024-10-23 12:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-19 12:51 [PATCH v10 0/8] block atomic writes for xfs John Garry
2024-10-19 12:51 ` [PATCH v10 1/8] block/fs: Pass an iocb to generic_atomic_write_valid() John Garry
2024-10-19 12:51 ` [PATCH v10 2/8] fs/block: Check for IOCB_DIRECT in generic_atomic_write_valid() John Garry
2024-10-19 12:51 ` [PATCH v10 3/8] block: Add bdev atomic write limits helpers John Garry
2024-10-19 12:51 ` [PATCH v10 4/8] fs: Export generic_atomic_write_valid() John Garry
2024-10-19 12:51 ` [PATCH v10 5/8] fs: iomap: Atomic write support John Garry
2024-10-20  8:21   ` Ritesh Harjani
2024-10-20 11:21     ` John Garry
2024-10-20 11:37       ` Ritesh Harjani
2024-10-19 12:51 ` [PATCH v10 6/8] xfs: Support atomic write for statx John Garry
2024-10-19 12:51 ` [PATCH v10 7/8] xfs: Validate atomic writes John Garry
2024-10-20  9:44   ` Ritesh Harjani
2024-10-20 11:09     ` John Garry
2024-10-20 11:41       ` Ritesh Harjani
2024-10-19 12:51 ` [PATCH v10 8/8] xfs: Support setting FMODE_CAN_ATOMIC_WRITE John Garry
2024-10-19 22:49 ` (subset) [PATCH v10 0/8] block atomic writes for xfs Jens Axboe
2024-10-19 22:50   ` Jens Axboe
2024-10-23 12:42     ` John Garry [this message]
2024-10-23 12:50       ` Carlos Maiolino
2024-10-24  6:32 ` Ojaswin Mujoo

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=e8a3a228-0367-43da-8cad-caaaa207f0e6@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