From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <yuchao0@huawei.com>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH v2] f2fs: avoid wrong decrypted data from disk
Date: Wed, 29 Aug 2018 21:03:31 -0700 [thread overview]
Message-ID: <20180830040331.GA97850@jaegeuk-macbookpro.roam.corp.google.com> (raw)
In-Reply-To: <ac310f4d-8ad8-bfd9-97f3-66e786f0f51e@huawei.com>
On 08/30, Chao Yu wrote:
> On 2018/8/30 9:48, 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>
> > ---
> > Change log from v1:
> > - move to bio != NULL
> >
> > fs/f2fs/data.c | 6 ++++++
> > 1 file changed, 6 insertions(+)
> >
> > diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
> > index 382c1ef9a9e4..159e411785e9 100644
> > --- a/fs/f2fs/data.c
> > +++ b/fs/f2fs/data.c
> > @@ -1556,6 +1556,12 @@ static int f2fs_mpage_readpages(struct address_space *mapping,
> > bio = NULL;
> > goto set_error_page;
> > }
> > + } else if (unlikely(f2fs_encrypted_file(inode))) {
>
> For android scenario, encryption becomes a common case now, so I think we can
> remove unlikely here.
>
> > + /*
> > + * If the page is under writeback, we need to wait for
> > + * its completion to see the correct decrypted data.
> > + */
> > + f2fs_wait_on_block_writeback(F2FS_I_SB(inode), block_nr);
> > }
>
> Look at this again, it seems f2fs_wait_on_block_writeback() is not related to
> f2fs_grab_read_bio(), so we can move it here to make code logic more clear:
>
> if (f2fs_encrypted_file(inode)) {
> /* */
> f2fs_wait_on_block_writeback(F2FS_I_SB(inode), block_nr);
> }
>
> Also, in f2fs_submit_page_read(), we need to adjust to:
>
> - f2fs_grab_read_bio()
> - f2fs_wait_on_block_writeback()
> - bio_add_page()
>
> How do you think?
Oh, yeah!
>
> Thanks,
>
> >
> > if (bio_add_page(bio, page, blocksize, 0) < blocksize)
> >
next prev parent reply other threads:[~2018-08-30 4:03 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 [this message]
2018-08-30 4:04 ` [f2fs-dev] [PATCH v3] " Jaegeuk Kim
2018-08-30 15:44 ` Chao Yu
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=20180830040331.GA97850@jaegeuk-macbookpro.roam.corp.google.com \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--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).