From: Jan Kara <jack@suse.cz>
To: 常凤楠 <changfengnan@qq.com>
Cc: tytso <tytso@mit.edu>, jack <jack@suse.com>,
adilger <adilger@dilger.ca>,
"darrick.wong" <darrick.wong@oracle.com>,
Fengnan Chang <changfengnan@hikvision.com>,
linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH v2] jbd2: avoid transaction reuse after reformatting
Date: Tue, 6 Oct 2020 12:33:26 +0200 [thread overview]
Message-ID: <20201006103326.GA6984@quack2.suse.cz> (raw)
In-Reply-To: <tencent_84E12D61F93979D8E588E980751B80B40B08@qq.com>
On Sat 03-10-20 14:30:24, 常凤楠 wrote:
> When format ext4 with lazy_journal_init=1, the previous transaction is still on disk,
> it is possible that the previous transaction will be used again during jbd2 recovery.
> Because the seed is changed, the CRC check will fail.
>
> Signed-off-by: Fengnan Chang <changfengnan@hikvision.com>
I've submitted v3 of the patch [1] which should not be mangled as this one...
Honza
[1] https://lore.kernel.org/linux-ext4/20201006103154.7130-1-jack@suse.cz
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
parent reply other threads:[~2020-10-06 10:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <tencent_84E12D61F93979D8E588E980751B80B40B08@qq.com>]
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=20201006103326.GA6984@quack2.suse.cz \
--to=jack@suse.cz \
--cc=adilger@dilger.ca \
--cc=changfengnan@hikvision.com \
--cc=changfengnan@qq.com \
--cc=darrick.wong@oracle.com \
--cc=jack@suse.com \
--cc=linux-ext4@vger.kernel.org \
--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).