ext4: don't allow ext4_free_blocks() to fail due to ENOMEM
authorTheodore Ts'o <tytso@mit.edu>
Sat, 13 Jul 2013 04:40:35 +0000 (00:40 -0400)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sun, 21 Jul 2013 00:16:08 +0000 (17:16 -0700)
commit1acc8ffbac40dfed3084d76d820f2dcbd8bc8d7d
treee145b042b76dcf718fe279cdecdb4f608ced0113
parent052a17d4964f869c3dd62ece4e16b1954452f66b
ext4: don't allow ext4_free_blocks() to fail due to ENOMEM

commit e7676a704ee0a1ef71a6b23760b5a8f6896cb1a1 upstream.

The filesystem should not be marked inconsistent if ext4_free_blocks()
is not able to allocate memory.  Unfortunately some callers (most
notably ext4_truncate) don't have a way to reflect an error back up to
the VFS.  And even if we did, most userspace applications won't deal
with most system calls returning ENOMEM anyway.

Reported-by: Nagachandra P <nagachandra@gmail.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
fs/ext4/mballoc.c