Re: [PATCH v3 02/11] reftable: fix resource leak in error path

From
Han-Wen Nienhuys <hidden>
Date
2021-12-13 16:44:59
Reply to
Ævar Arnfjörð Bjarmason, 2021-12-13
On Mon, Dec 13, 2021 at 5:21 PM Ævar Arnfjörð Bjarmason
[off-list ref] wrote:
Other things in the codebase don't check for NULL before feeding things
to reftable_free(), and our own free() has a coccicheck rule to catch
this sort of code, we should probably add reftable_free to that list...
Thanks, changed.
quoted
+     struct reftable_block_source source = { NULL };
Nit: It doesn't matter for semantics, but usually we use "{ 0 }", and
your 1/11 does too. Would be better to do that here for consistency.
I got a past review where someone complained about this. I don't mind
either way, but would rather not flipflop.
quoted
+     for (i = 0; i < sizeof(message)-1; i++) {
+             message[i] = (uint8_t)(rand() % 64 + ' ');
+     }
style: braces not needede.
Done.

-- 
Han-Wen Nienhuys - Google Munich
I work 80%. Don't expect answers from me on Fridays.
--

Google Germany GmbH, Erika-Mann-Strasse 33, 80636 Munich

Registergericht und -nummer: Hamburg, HRB 86891

Sitz der Gesellschaft: Hamburg

Geschäftsführer: Paul Manicle, Halimah DeLaine Prado
Thread (145 messages) 145 messages, 7 authors, last reply 2022-03-29
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help