public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: fengnan chang <fengnanchang@gmail.com>
To: yebin <yebin10@huawei.com>
Cc: "tytso@mit.edu" <tytso@mit.edu>,
	adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
	linux-kernel@vger.kernel.org, jack@suse.cz
Subject: Re: [PATCH RFC] jbd2: detect old record when do journal scan
Date: Fri, 19 Aug 2022 16:34:28 +0800	[thread overview]
Message-ID: <A602BE93-1AE5-43D7-B42B-D991E24AC933@gmail.com> (raw)
In-Reply-To: <62FF430D.9040405@huawei.com>

If there has system time calibration, system time has become smaller, what will be happen?
the journal maybe thought as corrupt?


> 2022年8月19日 16:00,yebin <yebin10@huawei.com> 写道:
> 
> ping...
> 
> On 2022/8/10 9:34, Ye Bin wrote:
>> As https://github.com/tytso/e2fsprogs/issues/120 describe tune2fs do not update
>> j_tail_sequence when do journal recovery. This maybe recover old journal record,
>> then will lead to file system corruption.
>> To avoid file system corruption in this case, if detect current transaction's
>> commit time earlier than previous transaction's commit time when do journal
>> scan, just return error.
>> 
>> Signed-off-by: Ye Bin <yebin10@huawei.com>
>> ---
>>  fs/jbd2/recovery.c | 11 ++++++++++-
>>  1 file changed, 10 insertions(+), 1 deletion(-)
>> 
>> diff --git a/fs/jbd2/recovery.c b/fs/jbd2/recovery.c
>> index f548479615c6..f3def21a96a5 100644
>> --- a/fs/jbd2/recovery.c
>> +++ b/fs/jbd2/recovery.c
>> @@ -812,8 +812,17 @@ static int do_one_pass(journal_t *journal,
>>  					break;
>>  				}
>>  			}
>> -			if (pass == PASS_SCAN)
>> +			if (pass == PASS_SCAN) {
>> +				if (commit_time < last_trans_commit_time) {
>> +					pr_err("JBD2: old journal record found "
>> +					       "in transaction %u\n",
>> +					       next_commit_ID);
>> +					err = -EFSBADCRC;
>> +					brelse(bh);
>> +					goto failed;
>> +				}
>>  				last_trans_commit_time = commit_time;
>> +			}
>>  			brelse(bh);
>>  			next_commit_ID++;
>>  			continue;
> 


  reply	other threads:[~2022-08-19  8:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-10  1:34 [PATCH RFC] jbd2: detect old record when do journal scan Ye Bin
2022-08-19  8:00 ` yebin
2022-08-19  8:34   ` fengnan chang [this message]
2022-08-19  9:54 ` Jan Kara
2022-08-23  9:17   ` yebin
2022-08-23 13:07     ` 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=A602BE93-1AE5-43D7-B42B-D991E24AC933@gmail.com \
    --to=fengnanchang@gmail.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=yebin10@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