From: Jan Kara <jack@suse.cz>
To: "zhangyi (F)" <yi.zhang@huawei.com>
Cc: linux-ext4@vger.kernel.org, tytso@mit.edu, jack@suse.cz,
adilger.kernel@dilger.ca, miaoxie@huawei.com
Subject: Re: [PATCH v3 2/4] jbd2: discard dirty data when forgetting an un-journalled buffer
Date: Mon, 28 Jan 2019 16:26:16 +0100 [thread overview]
Message-ID: <20190128152616.GF5858@quack2.suse.cz> (raw)
In-Reply-To: <1548419456-4331-3-git-send-email-yi.zhang@huawei.com>
On Fri 25-01-19 20:30:54, zhangyi (F) wrote:
> We do not unmap and clear dirty flag when forgetting a buffer without
> journal or does not belongs to any transaction, so the invalid dirty
> data may still be written to the disk later. It's fine if the
> corresponding block is never used before the next mount, and it's also
> fine that we invoke clean_bdev_aliases() related functions to unmap
> the block device mapping when re-allocating such freed block as data
> block. But this logic is somewhat fragile and risky that may lead to
> data corruption if we forget to clean bdev aliases. So, It's better to
> discard dirty data during forget time.
>
> We have been already handled all the cases of forgetting journalled
> buffer, this patch deal with the remaining two cases.
>
> - buffer is not journalled yet,
> - buffer is journalled but doesn't belongs to any transaction.
>
> We invoke __bforget() instead of __brelese() when forgetting an
> un-journalled buffer in jbd2_journal_forget(). After this patch we can
> remove all clean_bdev_aliases() related calls in ext4.
>
> Suggested-by: Jan Kara <jack@suse.cz>
> Signed-off-by: zhangyi (F) <yi.zhang@huawei.com>
Thanks for the patch! Just one small comment below:
> + /*
> + * The buffer is still not written to disk, we should
> + * attach this buffer to current transaction to prevent
> + * missing writing back when doing checkpoint before
> + * the current transaction complete submittion.
> + */
> + __jbd2_journal_temp_unlink_buffer(jh);
Calling __jbd2_journal_temp_unlink_buffer() is not needed when you know the
buffer does not belong to any transaction. Otherwise the patch looks good
to me so feel free to add:
Reviewed-by: Jan Kara <jack@suse.cz>
after fixing this.
Honza
> + clear_buffer_dirty(bh);
> + __jbd2_journal_file_buffer(jh, transaction, BJ_Forget);
> + spin_unlock(&journal->j_list_lock);
> }
>
> -not_jbd:
> jbd_unlock_bh_state(bh);
> __brelse(bh);
> drop:
> @@ -1643,6 +1673,11 @@ int jbd2_journal_forget (handle_t *handle, struct buffer_head *bh)
> handle->h_buffer_credits++;
> }
> return err;
> +
> +not_jbd:
> + jbd_unlock_bh_state(bh);
> + __bforget(bh);
> + goto drop;
> }
>
> /**
> --
> 2.7.4
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2019-01-28 15:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 12:30 [PATCH v3 0/4] ext4: fix a data corruption problem zhangyi (F)
2019-01-25 12:30 ` [PATCH v3 1/4] jbd2: make sure dirty flag is cleared while revorking a buffer which belongs to older transaction zhangyi (F)
2019-01-28 15:24 ` Jan Kara
2019-01-25 12:30 ` [PATCH v3 2/4] jbd2: discard dirty data when forgetting an un-journalled buffer zhangyi (F)
2019-01-28 15:26 ` Jan Kara [this message]
2019-01-25 12:30 ` [PATCH v3 3/4] ext4: cleanup clean_bdev_aliases() calls zhangyi (F)
2019-01-28 15:26 ` Jan Kara
2019-01-25 12:30 ` [PATCH v3 4/4] ext4: convert ext4_split_extent() to return requested length zhangyi (F)
2019-01-28 15: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=20190128152616.GF5858@quack2.suse.cz \
--to=jack@suse.cz \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=miaoxie@huawei.com \
--cc=tytso@mit.edu \
--cc=yi.zhang@huawei.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).