From: Jan Kara <jack@suse.cz>
To: Mauricio Faria de Oliveira <mfo@canonical.com>
Cc: Jan Kara <jack@suse.cz>,
linux-ext4@vger.kernel.org,
dann frazier <dann.frazier@canonical.com>
Subject: Re: [RFC PATCH v4 3/4] ext4: data=journal: fixes for ext4_page_mkwrite()
Date: Tue, 29 Sep 2020 13:48:25 +0200 [thread overview]
Message-ID: <20200929114825.GL10896@quack2.suse.cz> (raw)
In-Reply-To: <20200928194103.244692-4-mfo@canonical.com>
On Mon 28-09-20 16:41:02, Mauricio Faria de Oliveira wrote:
> These are two fixes for data journalling required by
> the next patch, discovered while testing it.
>
> First, the optimization to return early if all buffers
> are mapped is not appropriate for the next patch:
>
> The inode _must_ be added to the transaction's list in
> data=journal mode (so to write-protect pages on commit)
> thus we cannot return early there.
>
> Second, once that optimization to reduce transactions
> was disabled for data=journal mode, more transactions
> happened, and occasionally hit this warning message:
> 'JBD2: Spotted dirty metadata buffer'.
>
> Reason is, block_page_mkwrite() will set_buffer_dirty()
> before do_journal_get_write_access() that is there to
> prevent it. This issue was masked by the optimization.
>
> So, on data=journal use __block_write_begin() instead.
> This also requires page locking and len recalculation.
> (see block_page_mkwrite() for implementation details.)
>
> Finally, as Jan noted there is little sharing between
> data=journal and other modes in ext4_page_mkwrite().
>
> However, a prototype of ext4_journalled_page_mkwrite()
> showed there still would be lots of duplicated lines
> (tens of) that didn't seem worth it.
>
> Thus this patch ends up with an ugly goto to skip all
> non-data journalling code (to avoid long indentations,
> but that can be changed..) in the beginning, and just
> a conditional in the transaction section.
>
> Well, we skip a common part to data journalling which
> is the page truncated check, but we do it again after
> ext4_journal_start() when we re-acquire the page lock
> (so not to acquire the page lock twice needlessly for
> data journalling.)
>
> Signed-off-by: Mauricio Faria de Oliveira <mfo@canonical.com>
> Suggested-by: Jan Kara <jack@suse.cz>
The patch looks good to me. You can add:
Reviewed-by: Jan Kara <jack@suse.cz>
Honza
> ---
> fs/ext4/inode.c | 51 ++++++++++++++++++++++++++++++++++++++++++-------
> 1 file changed, 44 insertions(+), 7 deletions(-)
>
> diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c
> index bf596467c234..ac153e340a6f 100644
> --- a/fs/ext4/inode.c
> +++ b/fs/ext4/inode.c
> @@ -5977,9 +5977,17 @@ vm_fault_t ext4_page_mkwrite(struct vm_fault *vmf)
> if (err)
> goto out_ret;
>
> + /*
> + * On data journalling we skip straight to the transaction handle:
> + * there's no delalloc; page truncated will be checked later; the
> + * early return w/ all buffers mapped (calculates size/len) can't
> + * be used; and there's no dioread_nolock, so only ext4_get_block.
> + */
> + if (ext4_should_journal_data(inode))
> + goto retry_alloc;
> +
> /* Delalloc case is easy... */
> if (test_opt(inode->i_sb, DELALLOC) &&
> - !ext4_should_journal_data(inode) &&
> !ext4_nonda_switch(inode->i_sb)) {
> do {
> err = block_page_mkwrite(vma, vmf,
> @@ -6005,6 +6013,9 @@ vm_fault_t ext4_page_mkwrite(struct vm_fault *vmf)
> /*
> * Return if we have all the buffers mapped. This avoids the need to do
> * journal_start/journal_stop which can block and take a long time
> + *
> + * This cannot be done for data journalling, as we have to add the
> + * inode to the transaction's list to writeprotect pages on commit.
> */
> if (page_has_buffers(page)) {
> if (!ext4_walk_page_buffers(NULL, page_buffers(page),
> @@ -6029,16 +6040,42 @@ vm_fault_t ext4_page_mkwrite(struct vm_fault *vmf)
> ret = VM_FAULT_SIGBUS;
> goto out;
> }
> - err = block_page_mkwrite(vma, vmf, get_block);
> - if (!err && ext4_should_journal_data(inode)) {
> - if (ext4_walk_page_buffers(handle, page_buffers(page), 0,
> - PAGE_SIZE, NULL, do_journal_get_write_access)) {
> + /*
> + * Data journalling can't use block_page_mkwrite() because it
> + * will set_buffer_dirty() before do_journal_get_write_access()
> + * thus might hit warning messages for dirty metadata buffers.
> + */
> + if (!ext4_should_journal_data(inode)) {
> + err = block_page_mkwrite(vma, vmf, get_block);
> + } else {
> + lock_page(page);
> + size = i_size_read(inode);
> + /* Page got truncated from under us? */
> + if (page->mapping != mapping || page_offset(page) > size) {
> unlock_page(page);
> - ret = VM_FAULT_SIGBUS;
> + ret = VM_FAULT_NOPAGE;
> ext4_journal_stop(handle);
> goto out;
> }
> - ext4_set_inode_state(inode, EXT4_STATE_JDATA);
> +
> + if (page->index == size >> PAGE_SHIFT)
> + len = size & ~PAGE_MASK;
> + else
> + len = PAGE_SIZE;
> +
> + err = __block_write_begin(page, 0, len, ext4_get_block);
> + if (!err) {
> + if (ext4_walk_page_buffers(handle, page_buffers(page),
> + 0, len, NULL, do_journal_get_write_access)) {
> + unlock_page(page);
> + ret = VM_FAULT_SIGBUS;
> + ext4_journal_stop(handle);
> + goto out;
> + }
> + ext4_set_inode_state(inode, EXT4_STATE_JDATA);
> + } else {
> + unlock_page(page);
> + }
> }
> ext4_journal_stop(handle);
> if (err == -ENOSPC && ext4_should_retry_alloc(inode->i_sb, &retries))
> --
> 2.17.1
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2020-09-29 11:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 19:40 [RFC PATCH v4 0/4] ext4/jbd2: data=journal: write-protect pages on transaction commit Mauricio Faria de Oliveira
2020-09-28 19:41 ` [RFC PATCH v4 1/4] jbd2: introduce/export functions jbd2_journal_submit|finish_inode_data_buffers() Mauricio Faria de Oliveira
2020-09-29 2:24 ` Andreas Dilger
2020-09-30 21:36 ` Mauricio Faria de Oliveira
2020-09-28 19:41 ` [RFC PATCH v4 2/4] jbd2, ext4, ocfs2: introduce/use journal callbacks j_submit|finish_inode_data_buffers() Mauricio Faria de Oliveira
2020-09-29 2:28 ` Andreas Dilger
2020-09-28 19:41 ` [RFC PATCH v4 3/4] ext4: data=journal: fixes for ext4_page_mkwrite() Mauricio Faria de Oliveira
2020-09-29 2:34 ` Andreas Dilger
2020-09-29 11:48 ` Jan Kara [this message]
2020-09-28 19:41 ` [RFC PATCH v4 4/4] ext4: data=journal: write-protect pages on j_submit_inode_data_buffers() Mauricio Faria de Oliveira
2020-09-29 12:10 ` Jan Kara
2020-09-29 11:37 ` [RFC PATCH v4 0/4] ext4/jbd2: data=journal: write-protect pages on transaction commit Jan Kara
2020-09-30 22:59 ` Mauricio Faria de Oliveira
2020-10-01 7:34 ` Jan Kara
2020-10-01 12:46 ` Mauricio Faria de Oliveira
2020-10-02 8:39 ` Jan Kara
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=20200929114825.GL10896@quack2.suse.cz \
--to=jack@suse.cz \
--cc=dann.frazier@canonical.com \
--cc=linux-ext4@vger.kernel.org \
--cc=mfo@canonical.com \
/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).