ext2: Fix memory leak when truncate races ext2_get_blocks

Message ID 20170705230848.GA28983@debian.home
State Not Applicable
Headers show

Commit Message

Ernesto A. Fernández July 5, 2017, 11:08 p.m.
Buffer heads referencing indirect blocks may not be released if the file
is truncated at the right time. This happens because ext2_get_branch()
returns NULL when it finds the whole chain of indirect blocks already
set, and when truncate alters the chain this value of NULL is
treated as the address of the last head to be released. Handle this in the
same way as it's done after the got_it label.

Signed-off-by: Ernesto A. Fernández <ernesto.mnd.fernandez@gmail.com>
---
Despite trying I haven't actually managed to trigger this race. I tested
the patch by inducing regular failures in verify_chain().

 fs/ext2/inode.c | 1 +
 1 file changed, 1 insertion(+)

Patch

diff --git a/fs/ext2/inode.c b/fs/ext2/inode.c
index 2dcbd56..30163d0 100644
--- a/fs/ext2/inode.c
+++ b/fs/ext2/inode.c
@@ -659,6 +659,7 @@  static int ext2_get_blocks(struct inode *inode,
 				 */
 				err = -EAGAIN;
 				count = 0;
+				partial = chain + depth - 1;
 				break;
 			}
 			blk = le32_to_cpu(*(chain[depth-1].p + count));