btrfs: check_int: propagate out-of-memory error upwards

This issue was not causing any harm but IMO (and in the opinion of the
static code checker) it is better to propagate this error status upwards.

Signed-off-by: Stefan Behrens <sbehrens@giantdisaster.de>
Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
Signed-off-by: Chris Mason <clm@fb.com>
This commit is contained in:
Stefan Behrens 2014-05-09 15:28:07 +02:00 committed by Chris Mason
parent 61391d5622
commit 98806b446d
1 changed files with 4 additions and 1 deletions

View File

@ -1093,6 +1093,7 @@ static int btrfsic_process_metablock(
next_stack =
btrfsic_stack_frame_alloc();
if (NULL == next_stack) {
sf->error = -1;
btrfsic_release_block_ctx(
&sf->
next_block_ctx);
@ -1190,8 +1191,10 @@ static int btrfsic_process_metablock(
sf->next_block_ctx.datav[0];
next_stack = btrfsic_stack_frame_alloc();
if (NULL == next_stack)
if (NULL == next_stack) {
sf->error = -1;
goto one_stack_frame_backwards;
}
next_stack->i = -1;
next_stack->block = sf->next_block;