| commit | e5e24ada4f5578ae921539280e4716a41bfd95cc | [log] [tgz] |
|---|---|---|
| author | Arnaldo Carvalho de Melo <acme@redhat.com> | Mon Oct 24 11:25:44 2022 -0300 |
| committer | Arnaldo Carvalho de Melo <acme@redhat.com> | Mon Oct 24 11:25:44 2022 -0300 |
| tree | 8c9f447b9e5623681715f0df777844b64753804b | |
| parent | b72f5188856df0abf45e1a707856bb4e4e86153c [diff] |
core: Use zalloc() to make the code more robust Recently we had a problem where it was assumed that a field was initialized to zeros but the constructor was using malloc(), check all use and switch cus__new() to zalloc() to prevent such problems. The other cases are clone() operations, so no sense in zeroing newly allocated memory since it will be copied from some other similar struct. Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>