From: "Darrick J. Wong" <djwong@kernel.org>
To: "Ritesh Harjani (IBM)" <ritesh.list@gmail.com>,
John Garry <john.g.garry@oracle.com>,
brauner@kernel.org, Catherine Hoang <catherine.hoang@oracle.com>
Cc: linux-ext4@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>,
Jan Kara <jack@suse.cz>, Christoph Hellwig <hch@infradead.org>,
Ojaswin Mujoo <ojaswin@linux.ibm.com>,
linux-block@vger.kernel.org, Dave Chinner <david@fromorbit.com>,
linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: [ANNOUNCE] work tree for untorn filesystem writes
Date: Mon, 4 Nov 2024 16:43:41 -0800 [thread overview]
Message-ID: <20241105004341.GO21836@frogsfrogsfrogs> (raw)
Hi everyone,
Nobody else has stepped up to do this, so I've created a work branch for
the fs side of untorn writes:
https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git/log/?h=fs-atomic_2024-11-04
Can you all check this to make sure that I merged it correctly? And
maybe go test this on your storage hardware? :)
If all goes well then I think the next step is to ask brauner very
nicely if he'd consider adding this to the vfs trees for 6.13. If not
then I guess we can submit it ourselves, though we probably ought to ask
rothwell to add the branch to for-next asap.
PS: We're now past -rc6 so please reply quickly so that this doesn't
slip yet another cycle.
Catherine: John's on vacation all week, could you please send me the
latest versions of the xfs_io pwrite-atomic patch and the fstest for it?
--D
next reply other threads:[~2024-11-05 0:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 0:43 Darrick J. Wong [this message]
2024-11-05 11:19 ` [ANNOUNCE] work tree for untorn filesystem writes Carlos Maiolino
2024-11-05 12:52 ` Jens Axboe
2024-11-05 15:08 ` Theodore Ts'o
2024-11-05 15:11 ` Jens Axboe
2024-11-05 15:40 ` Darrick J. Wong
2024-11-05 15:54 ` Jens Axboe
2024-11-06 10:40 ` Christian Brauner
2024-11-07 13:38 ` Carlos Maiolino
2024-11-05 16:26 ` Ritesh Harjani
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=20241105004341.GO21836@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=brauner@kernel.org \
--cc=catherine.hoang@oracle.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=john.g.garry@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=ojaswin@linux.ibm.com \
--cc=ritesh.list@gmail.com \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).