summaryrefslogtreecommitdiffstats
path: root/crypto/pcompress.c
diff options
context:
space:
mode:
authorJaegeuk Kim <jaegeuk.kim@samsung.com>2012-12-19 15:28:39 +0900
committerJaegeuk Kim <jaegeuk.kim@samsung.com>2012-12-26 10:39:52 +0900
commit398b1ac5a57219823f942a8d3665b27ab99354de (patch)
tree7e4806bf658cdffdd977f83a1365f673b9f8e487 /crypto/pcompress.c
parent38e0abdcfb5e69aa61a1e9b474d434afc1c177a9 (diff)
f2fs: fix handling errors got by f2fs_write_inode
Ruslan reported that f2fs hangs with an infinite loop in f2fs_sync_file(): while (sync_node_pages(sbi, inode->i_ino, &wbc) == 0) f2fs_write_inode(inode, NULL); The reason was revealed that the cold flag is not set even thought this inode is a normal file. Therefore, sync_node_pages() skips to write node blocks since it only writes cold node blocks. The cold flag is stored to the node_footer in node block, and whenever a new node page is allocated, it is set according to its file type, file or directory. But, after sudden-power-off, when recovering the inode page, f2fs doesn't recover its cold flag. So, let's assign the cold flag in more right places. One more thing: If f2fs_write_inode() returns an error due to whatever situations, there would be no dirty node pages so that sync_node_pages() returns zero. (i.e., zero means nothing was written.) Reported-by: Ruslan N. Marchenko <me@ruff.mobi> Signed-off-by: Jaegeuk Kim <jaegeuk.kim@samsung.com>
Diffstat (limited to 'crypto/pcompress.c')
0 files changed, 0 insertions, 0 deletions