summaryrefslogtreecommitdiffstats
path: root/fs/nfsd
diff options
context:
space:
mode:
authorChao Yu <chao2.yu@samsung.com>2016-02-23 17:52:43 +0800
committerJaegeuk Kim <jaegeuk@kernel.org>2016-02-26 11:51:58 -0800
commit4356e48e64374ceac6e4313244eb65158a954b40 (patch)
tree4ebbd22dc8d0d7b73bde90d3d577297e10f6eb6e /fs/nfsd
parent80dd9c0e9db220697301e76b7b61f580ad9e8ecd (diff)
downloadop-kernel-dev-4356e48e64374ceac6e4313244eb65158a954b40.zip
op-kernel-dev-4356e48e64374ceac6e4313244eb65158a954b40.tar.gz
f2fs crypto: fix incorrect positioning for GCing encrypted data page
For now, flow of GCing an encrypted data page: 1) try to grab meta page in meta inode's mapping with index of old block address of that data page 2) load data of ciphertext into meta page 3) allocate new block address 4) write the meta page into new block address 5) update block address pointer in direct node page. Other reader/writer will use f2fs_wait_on_encrypted_page_writeback to check and wait on GCed encrypted data cached in meta page writebacked in order to avoid inconsistence among data page cache, meta page cache and data on-disk when updating. However, we will use new block address updated in step 5) as an index to lookup meta page in inner bio buffer. That would be wrong, and we will never find the GCing meta page, since we use the old block address as index of that page in step 1). This patch fixes the issue by adjust the order of step 1) and step 3), and in step 1) grab page with index generated in step 3). Signed-off-by: Chao Yu <chao2.yu@samsung.com> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'fs/nfsd')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud