Btrfs: do not warn_on when we cannot alloc a page for an extent buffer
authorJosef Bacik <jbacik@fusionio.com>
Fri, 5 Oct 2012 20:43:45 +0000 (16:43 -0400)
committerChris Mason <chris.mason@fusionio.com>
Tue, 9 Oct 2012 13:20:43 +0000 (09:20 -0400)
It's just annoying and the user will have gotten a nice OOM killer message
so they are already fully aware they are screwed :).  Thanks,

Reported-by: Jérôme Poulin <jeromepoulin@gmail.com>
Signed-off-by: Josef Bacik <jbacik@fusionio.com>
fs/btrfs/extent_io.c

index 8c37cb64be7adf7e9dd20a3d3476b57a1e8ad81c..7dc69b38548df0874be2ca728f7c582a69f38c69 100644 (file)
@@ -4249,10 +4249,8 @@ struct extent_buffer *alloc_extent_buffer(struct extent_io_tree *tree,
 
        for (i = 0; i < num_pages; i++, index++) {
                p = find_or_create_page(mapping, index, GFP_NOFS);
-               if (!p) {
-                       WARN_ON(1);
+               if (!p)
                        goto free_eb;
-               }
 
                spin_lock(&mapping->private_lock);
                if (PagePrivate(p)) {