"Michael S. Tsirkin" <mst@xxxxxxxxxx> writes:
> foo = kmalloc(SIZE, GFP_KERNEL);
> if (!foo)
> goto err_foo;
>
> foo->bar = kmalloc(SIZE, GFP_KERNEL);
> if (!foo->bar)
> goto err_bar;
> ...
>
> kfree(foo->bar);
> err_bar:
>
> kfree(foo);
> err_foo:
>
> return ret;
I believe the CodingStyle already contain far too much personal style to
be useful as real style guide. FWIW, I prefer a single error label, at
the "cost" of additional tests in the error path:
foo = kmalloc(SIZE, GFP_KERNEL);
if (!foo)
goto err;
foo->bar = kmalloc(SIZE, GFP_KERNEL);
if (!foo->bar)
goto err;
...
if (ret)
goto err;
return 0;
err:
if (foo)
kfree(foo->bar);
kfree(foo);
return ret;
The advantage is that I don't have to manage X different labels,
ensuring that they have the order is correct if some part of the
function is refactored etc. That tends to get too complicated for my
simple brain. And since the error path is rarely tested, complicated
equals buggy.
My sample will of course trigger all those nice "optimizing the error
path" patches, but I ignore those anyway so that's not a big deal.
Bjørn
_______________________________________________
Virtualization mailing list
Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
