[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <96cb2069-a8e2-4723-802c-3ad4ba3e3d42@oracle.com>
Date: Fri, 7 Jun 2024 07:16:14 +0100
From: John Garry <john.g.garry@...cle.com>
To: axboe@...nel.dk, viro@...iv.linux.org.uk, brauner@...nel.org, jack@...e.cz
Cc: linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-nvme@...ts.infradead.org, linux-fsdevel@...r.kernel.org,
tytso@....edu, jbongio@...gle.com, linux-scsi@...r.kernel.org,
ojaswin@...ux.ibm.com, linux-aio@...ck.org,
linux-btrfs@...r.kernel.org, io-uring@...r.kernel.org,
nilay@...ux.ibm.com, ritesh.list@...il.com, willy@...radead.org,
kbusch@...nel.org, hch@....de, sagi@...mberg.me, jejb@...ux.ibm.com,
martin.petersen@...cle.com, djwong@...nel.org, dchinner@...hat.com
Subject: Re: [PATCH v7 0/9] block atomic writes
On 02/06/2024 15:09, John Garry wrote:
> This series introduces a proposal to implementing atomic writes in the
> kernel for torn-write protection.
>
> This series takes the approach of adding a new "atomic" flag to each of
> pwritev2() and iocb->ki_flags - RWF_ATOMIC and IOCB_ATOMIC, respectively.
> When set, these indicate that we want the write issued "atomically".
Hi vfs maintainers, Jens,
Can you please let me know if you have any issues with this series?
Specifically the first few patches.
This work has been on the lists for a year now, and most seem happy /
content with it.
I really would like this to be this merged in this cycle.
Note that I plan to post a new series version soon, addressing comments
from Hannes and Christoph, but they are not major changes.
Thanks,
John
Powered by blists - more mailing lists