From: Jan Kara <jack@suse.cz>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: Jan Kara <jack@suse.cz>, Shijie Luo <luoshijie1@huawei.com>,
linux-ext4@vger.kernel.org, linfeilong@huawei.com
Subject: Re: [PATCH] jbd2: remove useless variable chksum_seen in do_one_pass
Date: Wed, 19 Aug 2020 10:48:58 +0200 [thread overview]
Message-ID: <20200819084858.GF1902@quack2.suse.cz> (raw)
In-Reply-To: <20200818191459.GC162457@mit.edu>
On Tue 18-08-20 15:14:59, Theodore Y. Ts'o wrote:
> I wonder if this is even cleaner? What do folks think?
>
> - Ted
Yup, looks good to me. Feel free to add:
Reviewed-by: Jan Kara <jack@suse.cz>
once you add proper changelog and signed-off-by.
Honza
>
> diff --git a/fs/jbd2/recovery.c b/fs/jbd2/recovery.c
> index 2ed278f0dced..4373abbfd19a 100644
> --- a/fs/jbd2/recovery.c
> +++ b/fs/jbd2/recovery.c
> @@ -690,14 +690,11 @@ static int do_one_pass(journal_t *journal,
> * number. */
> if (pass == PASS_SCAN &&
> jbd2_has_feature_checksum(journal)) {
> - int chksum_err, chksum_seen;
> struct commit_header *cbh =
> (struct commit_header *)bh->b_data;
> unsigned found_chksum =
> be32_to_cpu(cbh->h_chksum[0]);
>
> - chksum_err = chksum_seen = 0;
> -
> if (info->end_transaction) {
> journal->j_failed_commit =
> info->end_transaction;
> @@ -705,42 +702,23 @@ static int do_one_pass(journal_t *journal,
> break;
> }
>
> - if (crc32_sum == found_chksum &&
> - cbh->h_chksum_type == JBD2_CRC32_CHKSUM &&
> - cbh->h_chksum_size ==
> - JBD2_CRC32_CHKSUM_SIZE)
> - chksum_seen = 1;
> - else if (!(cbh->h_chksum_type == 0 &&
> - cbh->h_chksum_size == 0 &&
> - found_chksum == 0 &&
> - !chksum_seen))
> - /*
> - * If fs is mounted using an old kernel and then
> - * kernel with journal_chksum is used then we
> - * get a situation where the journal flag has
> - * checksum flag set but checksums are not
> - * present i.e chksum = 0, in the individual
> - * commit blocks.
> - * Hence to avoid checksum failures, in this
> - * situation, this extra check is added.
> - */
> - chksum_err = 1;
> -
> - if (chksum_err) {
> - info->end_transaction = next_commit_ID;
> -
> - if (!jbd2_has_feature_async_commit(journal)) {
> - journal->j_failed_commit =
> - next_commit_ID;
> - brelse(bh);
> - break;
> - }
> - }
> + /* Neither checksum match nor unused? */
> + if (!((crc32_sum == found_chksum &&
> + cbh->h_chksum_type ==
> + JBD2_CRC32_CHKSUM &&
> + cbh->h_chksum_size ==
> + JBD2_CRC32_CHKSUM_SIZE) ||
> + (cbh->h_chksum_type == 0 &&
> + cbh->h_chksum_size == 0 &&
> + found_chksum == 0)))
> + goto chksum_error;
> +
> crc32_sum = ~0;
> }
> if (pass == PASS_SCAN &&
> !jbd2_commit_block_csum_verify(journal,
> bh->b_data)) {
> + chksum_error:
> info->end_transaction = next_commit_ID;
>
> if (!jbd2_has_feature_async_commit(journal)) {
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2020-08-19 8:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 2:21 [PATCH] jbd2: remove useless variable chksum_seen in do_one_pass Shijie Luo
2020-08-18 10:48 ` Jan Kara
2020-08-18 11:33 ` Shijie Luo
2020-08-18 19:14 ` Theodore Y. Ts'o
2020-08-19 2:02 ` Shijie Luo
2020-08-19 8:48 ` Jan Kara [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=20200819084858.GF1902@quack2.suse.cz \
--to=jack@suse.cz \
--cc=linfeilong@huawei.com \
--cc=linux-ext4@vger.kernel.org \
--cc=luoshijie1@huawei.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).