From: Christoph Hellwig <hch@infradead.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Jan Kara <jack@suse.cz>, Matthew Wilcox <willy@infradead.org>,
Brian Foster <bfoster@redhat.com>, Linux-MM <linux-mm@kvack.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-xfs <linux-xfs@vger.kernel.org>,
Hugh Dickins <hughd@google.com>,
Namjae Jeon <namjae.jeon@samsung.com>,
Ashish Sangwan <a.sangwan@samsung.com>,
Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: writeback completion soft lockup BUG in folio_wake_bit()
Date: Wed, 30 Mar 2022 08:55:46 -0700 [thread overview]
Message-ID: <YkR9gu4Ye2uydkTd@infradead.org> (raw)
In-Reply-To: <YjYDaBnN36zggeGa@mit.edu>
On Sat, Mar 19, 2022 at 12:23:04PM -0400, Theodore Ts'o wrote:
> So the thing that I've been waiting to do for a while is to replace
> the whole data=ordered vs data=writeback and dioread_nolock and
> dioread_lock is a complete reworking of the ext4 buffered writeback
> path, where we write the data blocks *first*, and only then update the
> ext4 metadata.
> *) Determining where the new allocated data blockblocks should be, and
> preventing those blocks from being used for any other purposes, but
> *not* updating the file system metadata to reflect that change.
>
> *) Submit the data block write
>
> *) On write completion, update the metadata blocks in a kernel thread.
I think that would be easily done by switching to the iomap buffered
I/O code, which is very much built around that model.
prev parent reply other threads:[~2022-03-30 15:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YjDj3lvlNJK/IPiU@bfoster>
[not found] ` <YjJPu/3tYnuKK888@casper.infradead.org>
[not found] ` <CAHk-=wgPTWoXCa=JembExs8Y7fw7YUi9XR0zn1xaxWLSXBN_vg@mail.gmail.com>
[not found] ` <YjNN5SzHELGig+U4@casper.infradead.org>
[not found] ` <CAHk-=wiZvOpaP0DVyqOnspFqpXRaT6q53=gnA2psxnf5dbt7bw@mail.gmail.com>
2022-03-17 21:16 ` writeback completion soft lockup BUG in folio_wake_bit() Matthew Wilcox
2022-03-17 22:52 ` Dave Chinner
2022-03-18 13:16 ` Jan Kara
2022-03-18 18:56 ` Linus Torvalds
2022-03-19 16:23 ` Theodore Ts'o
2022-03-30 15:55 ` Christoph Hellwig [this message]
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=YkR9gu4Ye2uydkTd@infradead.org \
--to=hch@infradead.org \
--cc=a.sangwan@samsung.com \
--cc=bfoster@redhat.com \
--cc=hughd@google.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=namjae.jeon@samsung.com \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=willy@infradead.org \
/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).