From: Jaegeuk Kim Date: Wed, 13 Mar 2013 08:45:15 +0000 (+0900) Subject: f2fs: fix to unlock node page when it was truncated X-Git-Tag: v3.10-rc1~45^2~66 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=12faafe45477244bc32e2c58f74f7305cc7e84fa;p=profile%2Fivi%2Fkernel-x86-ivi.git f2fs: fix to unlock node page when it was truncated If the node page was truncated, its block address became zero. This means that we don't need to write the node page, but have to unlock NODE_WRITE, decrease the number of dirty node pages, and then unlock_page before returning the f2fs_write_node_page with zero. Reviewed-by: Namjae Jeon Signed-off-by: Jaegeuk Kim --- diff --git a/fs/f2fs/node.c b/fs/f2fs/node.c index e275218..3dc63f4 100644 --- a/fs/f2fs/node.c +++ b/fs/f2fs/node.c @@ -1106,15 +1106,15 @@ static int f2fs_write_node_page(struct page *page, /* This page is already truncated */ if (ni.blk_addr == NULL_ADDR) - return 0; + goto out; set_page_writeback(page); /* insert node offset */ write_node_page(sbi, page, nid, ni.blk_addr, &new_addr); set_node_addr(sbi, &ni, new_addr); +out: dec_page_count(sbi, F2FS_DIRTY_NODES); - mutex_unlock_op(sbi, NODE_WRITE); unlock_page(page); return 0;