diff options
| author | Theodore Ts'o <tytso@mit.edu> | 2013-07-13 00:40:35 -0400 |
|---|---|---|
| committer | Theodore Ts'o <tytso@mit.edu> | 2013-07-13 00:40:35 -0400 |
| commit | e7676a704ee0a1ef71a6b23760b5a8f6896cb1a1 (patch) | |
| tree | a0baabd652713be5622578c8783dabfaf1141687 /drivers | |
| parent | bdafe42aaf72859166f784f0fad3e6b4a815fa6d (diff) | |
| download | linux-e7676a704ee0a1ef71a6b23760b5a8f6896cb1a1.tar.bz2 | |
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 'drivers')
0 files changed, 0 insertions, 0 deletions