This is a note to let you know that I've just added the patch titled
ext4: don't allow ext4_free_blocks() to fail due to ENOMEM
to the 3.10-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
ext4-don-t-allow-ext4_free_blocks-to-fail-due-to-enomem.patch
and it can be found in the queue-3.10 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.
>From e7676a704ee0a1ef71a6b23760b5a8f6896cb1a1 Mon Sep 17 00:00:00 2001
From: Theodore Ts'o <[email protected]>
Date: Sat, 13 Jul 2013 00:40:35 -0400
Subject: ext4: don't allow ext4_free_blocks() to fail due to ENOMEM
From: Theodore Ts'o <[email protected]>
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 <[email protected]>
Signed-off-by: "Theodore Ts'o" <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
---
fs/ext4/mballoc.c | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)
--- a/fs/ext4/mballoc.c
+++ b/fs/ext4/mballoc.c
@@ -4735,11 +4735,16 @@ do_more:
* blocks being freed are metadata. these blocks shouldn't
* be used until this transaction is committed
*/
+ retry:
new_entry = kmem_cache_alloc(ext4_free_data_cachep, GFP_NOFS);
if (!new_entry) {
- ext4_mb_unload_buddy(&e4b);
- err = -ENOMEM;
- goto error_return;
+ /*
+ * We use a retry loop because
+ * ext4_free_blocks() is not allowed to fail.
+ */
+ cond_resched();
+ congestion_wait(BLK_RW_ASYNC, HZ/50);
+ goto retry;
}
new_entry->efd_start_cluster = bit;
new_entry->efd_group = block_group;
Patches currently in stable-queue which might be from [email protected] are
queue-3.10/ext4-fix-corruption-when-online-resizing-a-fs-with-1k-block-size.patch
queue-3.10/ext4-fix-ext4_get_group_number.patch
queue-3.10/jbd2-fix-theoretical-race-in-jbd2__journal_restart.patch
queue-3.10/ext4-don-t-allow-ext4_free_blocks-to-fail-due-to-enomem.patch
queue-3.10/ext4-fix-data-offset-overflow-in-ext4_xattr_fiemap-on-32-bit-archs.patch
queue-3.10/ext4-fix-overflow-when-counting-used-blocks-on-32-bit-architectures.patch
queue-3.10/ext3-ext4-don-t-mess-with-dir_file-f_pos-in-htree_dirblock_to_tree.patch
queue-3.10/ext4-check-error-return-from-ext4_write_inline_data_end.patch
queue-3.10/ext4-fix-overflows-in-seek_hole-seek_data-implementations.patch
queue-3.10/ext4-fix-data-offset-overflow-on-32-bit-archs-in-ext4_inline_data_fiemap.patch
queue-3.10/jbd2-move-superblock-checksum-calculation-to-jbd2_write_superblock.patch
queue-3.10/ext4-don-t-show-usrquota-grpquota-twice-in-proc-mounts.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
