From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Andreas Dilger <adilger@dilger.ca>
Cc: Jan Kara <jack@suse.cz>,
linux-ext4@vger.kernel.org,
Fengnan Chang <changfengnan@hikvision.com>,
changfengnan <fengnanchang@foxmail.com>
Subject: Re: [PATCH v4] jbd2: avoid transaction reuse after reformatting
Date: Thu, 8 Oct 2020 22:16:51 -0400 [thread overview]
Message-ID: <20201009021651.GI235506@mit.edu> (raw)
In-Reply-To: <AF239FDD-1550-4D24-B2A4-C015689C9203@dilger.ca>
On Thu, Oct 08, 2020 at 02:13:02PM -0600, Andreas Dilger wrote:
> On Oct 7, 2020, at 2:13 AM, Jan Kara <jack@suse.cz> wrote:
> >
> > From: changfengnan <fengnanchang@foxmail.com>
> >
> > When ext4 is formatted with lazy_journal_init=1 and transactions from
> > the previous filesystem are still on disk, it is possible that they are
> > considered during a recovery after a crash. Because the checksum seed
> > has changed, the CRC check will fail, and the journal recovery fails
> > with checksum error although the journal is otherwise perfectly valid.
> > Fix the problem by checking commit block time stamps to determine
> > whether the data in the journal block is just stale or whether it is
> > indeed corrupt.
> >
> > Reported-by: kernel test robot <lkp@intel.com>
> > Signed-off-by: Fengnan Chang <changfengnan@hikvision.com>
> > Signed-off-by: Jan Kara <jack@suse.cz>
>
> Reviewed-by: Andreas Dilger <adilger@dilger.ca>
>
> NB: one trivial formatting cleanup if patch is refreshed
>
Applied, thanks. I fixed the trivial format cleanup you pointed out,
plus a whitespace fix pointed out by checkpatch.
- Ted
next prev parent reply other threads:[~2020-10-09 2:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 8:13 [PATCH v4] jbd2: avoid transaction reuse after reformatting Jan Kara
2020-10-08 20:13 ` Andreas Dilger
2020-10-09 2:16 ` Theodore Y. Ts'o [this message]
[not found] ` <tencent_909C05B896D07CD8BC84F2EC74B03A1A4007@qq.com>
2020-10-12 15:29 ` 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=20201009021651.GI235506@mit.edu \
--to=tytso@mit.edu \
--cc=adilger@dilger.ca \
--cc=changfengnan@hikvision.com \
--cc=fengnanchang@foxmail.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.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