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)
committerTheodore Ts'o <tytso@mit.edu>
Sat, 13 Jul 2013 04:40:35 +0000 (00:40 -0400)
commite7676a704ee0a1ef71a6b23760b5a8f6896cb1a1
treea0baabd652713be5622578c8783dabfaf1141687
parentbdafe42aaf72859166f784f0fad3e6b4a815fa6d
ext4: don't allow ext4_free_blocks() to fail due to ENOMEM

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>
Cc: stable@vger.kernel.org
fs/ext4/mballoc.c