From: Chao Yu <chao@kernel.org>
To: Weichao Guo <guoweichao@huawei.com>,
yuchao0@huawei.com, jaegeuk@kernel.org
Cc: heyunlei@huawei.com, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH v6] f2fs: support in-memory inode checksum when checking consistency
Date: Fri, 9 Mar 2018 20:32:54 +0800 [thread overview]
Message-ID: <a47f103a-4a33-fb1f-e632-51fb5e27643c@kernel.org> (raw)
In-Reply-To: <20180309151021.142737-1-guoweichao@huawei.com>
On 2018/3/9 23:10, Weichao Guo wrote:
> Enable in-memory inode checksum to protect metadata blocks from
> in-memory scribbles when checking consistency, which has no
> performance requirements.
>
> Signed-off-by: Weichao Guo <guoweichao@huawei.com>
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Thanks,
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
next prev parent reply other threads:[~2018-03-09 12:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 15:10 [PATCH v6] f2fs: support in-memory inode checksum when checking consistency Weichao Guo
2018-03-09 12:32 ` Chao Yu [this message]
2018-06-12 14:36 ` Chao Yu
2018-06-22 7:16 ` Chao Yu
2018-07-15 6:38 ` Chao Yu
2018-07-23 11:21 ` Jaegeuk Kim
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=a47f103a-4a33-fb1f-e632-51fb5e27643c@kernel.org \
--to=chao@kernel.org \
--cc=guoweichao@huawei.com \
--cc=heyunlei@huawei.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=yuchao0@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).