Btrfs: do not warn_on when we cannot alloc a page for an extent buffer
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>
This commit is contained in:
@@ -4249,10 +4249,8 @@ struct extent_buffer *alloc_extent_buffer(struct extent_io_tree *tree,
|
|||||||
|
|
||||||
for (i = 0; i < num_pages; i++, index++) {
|
for (i = 0; i < num_pages; i++, index++) {
|
||||||
p = find_or_create_page(mapping, index, GFP_NOFS);
|
p = find_or_create_page(mapping, index, GFP_NOFS);
|
||||||
if (!p) {
|
if (!p)
|
||||||
WARN_ON(1);
|
|
||||||
goto free_eb;
|
goto free_eb;
|
||||||
}
|
|
||||||
|
|
||||||
spin_lock(&mapping->private_lock);
|
spin_lock(&mapping->private_lock);
|
||||||
if (PagePrivate(p)) {
|
if (PagePrivate(p)) {
|
||||||
|
Reference in New Issue
Block a user