02 Apr, 2014
1 commit
-
We should unlock page in ->readpage() path and also should unlock & release page
in error path of ->write_begin() to avoid deadlock or memory leak.
So let's add release code to fix the problem when we fail to read inline data.Signed-off-by: Chao Yu
Signed-off-by: Jaegeuk Kim
14 Jan, 2014
1 commit
-
"boo sync" parameter is never referenced in f2fs_wait_on_page_writeback.
We should remove this parameter.Signed-off-by: Yuan Zhong
Signed-off-by: Jaegeuk Kim
06 Jan, 2014
6 commits
-
Here is a case which could read inline page data not from first page.
1. write inline data
2. lseek to offset 4096
3. read 4096 bytes from offset 4096
(read_inline_data read inline data page to non-first page,
And previously VFS has add this page to page cache)
4. ftruncate offset 8192
5. read 4096 bytes from offset 4096
(we meet this updated page with inline data in cache)So we should leave this page with inited data and uptodate flag
for this case.Change log from v1:
o fix a deadlock bugSigned-off-by: Chao Yu
Signed-off-by: Jaegeuk Kim -
Change log from v1:
o reduce unneeded memset in __f2fs_convert_inline_data>From 58796be2bd2becbe8d52305210fb2a64e7dd80b6 Mon Sep 17 00:00:00 2001
From: Chao Yu
Date: Mon, 30 Dec 2013 09:21:33 +0800
Subject: [PATCH] f2fs: avoid to left uninitialized data in page when read
inline dataWe left uninitialized data in the tail of page when we read an inline data
page. So let's initialize left part of the page excluding inline data region.Signed-off-by: Chao Yu
Signed-off-by: Jaegeuk Kim -
The get_dnode_of_data nullifies inode and node page when error is occurred.
There are two cases that passes inode page into get_dnode_of_data().
1. make_empty_dir()
-> get_new_data_page()
-> f2fs_reserve_block(ipage)
-> get_dnode_of_data()2. f2fs_convert_inline_data()
-> __f2fs_convert_inline_data()
-> f2fs_reserve_block(ipage)
-> get_dnode_of_data()This patch adds correct error handling codes when get_dnode_of_data() returns
an error.At first, f2fs_reserve_block() calls f2fs_put_dnode() whenever reserve_new_block
returns an error.
So, the rule of f2fs_reserve_block() is to nullify inode page when there is any
error internally.Finally, two callers of f2fs_reserve_block() should call f2fs_put_dnode()
appropriately if they got an error since successful f2fs_reserve_block().Signed-off-by: Jaegeuk Kim
-
This patch adds a inline_data recovery routine with the following policy.
[prev.] [next] of inline_data flag
o o -> recover inline_data
o x -> remove inline_data, and then recover data blocks
x o -> remove inline_data, and then recover inline_data
x x -> recover data blocksSigned-off-by: Jaegeuk Kim
-
This patch adds the number of inline_data files into the status information.
Note that the number is reset whenever the filesystem is newly mounted.Signed-off-by: Jaegeuk Kim
-
Change log from v1:
o handle NULL pointer of grab_cache_page_write_begin() pointed by Chao Yu.This patch refactors f2fs_convert_inline_data to check a couple of conditions
internally for deciding whether it needs to convert inline_data or not.So, the new f2fs_convert_inline_data initially checks:
1) f2fs_has_inline_data(), and
2) the data size to be changed.If the inode has inline_data but the size to fill is less than MAX_INLINE_DATA,
then we don't need to convert the inline_data with data allocation.Signed-off-by: Jaegeuk Kim
26 Dec, 2013
1 commit
-
Functions to implement inline data read/write, and move inline data to
normal data block when file size exceeds inline data limitation.Signed-off-by: Huajun Li
Signed-off-by: Haicheng Li
Signed-off-by: Weihong Xu
Signed-off-by: Jaegeuk Kim
