From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3] f2fs: avoid wrong decrypted data from disk
Date: Thu, 30 Aug 2018 23:44:48 +0800 [thread overview]
Message-ID: <73a30772-98f3-620b-720e-2121da85abec@kernel.org> (raw)
In-Reply-To: <20180830040458.GB97850@jaegeuk-macbookpro.roam.corp.google.com>
On 2018/8/30 12:04, Jaegeuk Kim wrote:
> 1. Create a file in an encrypted directory
> 2. Do GC & drop caches
> 3. Read stale data before its bio for metapage was not issued yet
>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Thanks,
next prev parent reply other threads:[~2018-08-30 15:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 22:52 [PATCH] f2fs: avoid wrong decrypted data from disk Jaegeuk Kim
2018-08-29 2:14 ` Chao Yu
2018-08-30 1:48 ` [PATCH v2] " Jaegeuk Kim
2018-08-30 2:20 ` Chao Yu
2018-08-30 4:03 ` Jaegeuk Kim
2018-08-30 4:04 ` [f2fs-dev] [PATCH v3] " Jaegeuk Kim
2018-08-30 15:44 ` Chao Yu [this message]
2018-08-30 6:29 ` [f2fs-dev] [PATCH] " Sahitya Tummala
2018-08-30 7:49 ` Sahitya Tummala
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=73a30772-98f3-620b-720e-2121da85abec@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).