summaryrefslogtreecommitdiffstats
path: root/fs/ext4/extents_status.c
diff options
context:
space:
mode:
authorTheodore Ts'o <tytso@mit.edu>2013-07-13 06:40:35 +0200
committerTheodore Ts'o <tytso@mit.edu>2013-07-13 06:40:35 +0200
commite7676a704ee0a1ef71a6b23760b5a8f6896cb1a1 (patch)
treea0baabd652713be5622578c8783dabfaf1141687 /fs/ext4/extents_status.c
parentext4: fix spelling errors and a comment in extent_status tree (diff)
downloadlinux-e7676a704ee0a1ef71a6b23760b5a8f6896cb1a1.tar.xz
linux-e7676a704ee0a1ef71a6b23760b5a8f6896cb1a1.zip
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
Diffstat (limited to 'fs/ext4/extents_status.c')
0 files changed, 0 insertions, 0 deletions