a trivial clean up of zram_meta_alloc() error handling.

Signed-off-by: Sergey Senozhatsky <[email protected]>
---
 drivers/block/zram/zram_drv.c | 14 ++++++--------
 1 file changed, 6 insertions(+), 8 deletions(-)

diff --git a/drivers/block/zram/zram_drv.c b/drivers/block/zram/zram_drv.c
index bd8bda3..369fe56 100644
--- a/drivers/block/zram/zram_drv.c
+++ b/drivers/block/zram/zram_drv.c
@@ -318,31 +318,29 @@ static struct zram_meta *zram_meta_alloc(u64 disksize)
 {
        size_t num_pages;
        struct zram_meta *meta = kmalloc(sizeof(*meta), GFP_KERNEL);
+
        if (!meta)
-               goto out;
+               return NULL;
 
        num_pages = disksize >> PAGE_SHIFT;
        meta->table = vzalloc(num_pages * sizeof(*meta->table));
        if (!meta->table) {
                pr_err("Error allocating zram address table\n");
-               goto free_meta;
+               goto out_error;
        }
 
        meta->mem_pool = zs_create_pool(GFP_NOIO | __GFP_HIGHMEM);
        if (!meta->mem_pool) {
                pr_err("Error creating memory pool\n");
-               goto free_table;
+               goto out_error;
        }
 
        return meta;
 
-free_table:
+out_error:
        vfree(meta->table);
-free_meta:
        kfree(meta);
-       meta = NULL;
-out:
-       return meta;
+       return NULL;
 }
 
 static void update_position(u32 *index, int *offset, struct bio_vec *bvec)
-- 
2.2.1.209.g41e5f3a

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to