From: Ryusuke Konishi Date: Sun, 31 Jan 2010 03:39:50 +0000 (+0900) Subject: nilfs2: fix potential leak of dirty data on umount X-Git-Tag: v2.6.33-rc7~18^2 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=3256a05531b1164a9c138da701b922a113bddf82;p=profile%2Fivi%2Fkernel-adaptation-intel-automotive.git nilfs2: fix potential leak of dirty data on umount This fixes incorrect usage of nilfs_segctor_confirm() test function in nilfs_segctor_destroy(); nilfs_segctor_confirm() returns zero if the filesystem is not clean, so its use in nilfs_segctor_destroy() needs inversion. Signed-off-by: Ryusuke Konishi --- diff --git a/fs/nilfs2/segment.c b/fs/nilfs2/segment.c index 17584c5..105b508 100644 --- a/fs/nilfs2/segment.c +++ b/fs/nilfs2/segment.c @@ -2829,7 +2829,7 @@ static void nilfs_segctor_destroy(struct nilfs_sc_info *sci) || sci->sc_seq_request != sci->sc_seq_done); spin_unlock(&sci->sc_state_lock); - if (flag || nilfs_segctor_confirm(sci)) + if (flag || !nilfs_segctor_confirm(sci)) nilfs_segctor_write_out(sci); WARN_ON(!list_empty(&sci->sc_copied_buffers));