diff options
| author | Theodore Ts'o <tytso@mit.edu> | 2013-07-13 00:40:35 -0400 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2013-07-21 18:21:33 -0700 |
| commit | 7557d8d5a46aaa4d0ec98bffdeedf9f3c7464088 (patch) | |
| tree | 6606be5385d264bfb902f499c16540676dbba802 /arch/arm/mm | |
| parent | bbb1d9216c9d8f5ac0aca90719512deae7f989ea (diff) | |
| download | linux-3.10-7557d8d5a46aaa4d0ec98bffdeedf9f3c7464088.tar.gz linux-3.10-7557d8d5a46aaa4d0ec98bffdeedf9f3c7464088.tar.bz2 linux-3.10-7557d8d5a46aaa4d0ec98bffdeedf9f3c7464088.zip | |
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>
Diffstat (limited to 'arch/arm/mm')
0 files changed, 0 insertions, 0 deletions