Comment # 3 on bug 929108 from Andreas Stieger

Marcus (Brenden, Miklos) sent to upstream ML just now. Closing.

-------- Forwarded Message --------
Subject: memory leak - __acl_init_obj, __new_var_obj_p
Date: Tue, 14 Jul 2015 11:45:56 +0200
From: Andreas Stieger <astieger@suse.com>
Organization: SUSE Linux GmbH
To: acl-devel@nongnu.org

Hello,

> [  124s] ================================================================= != ~
> [  124s] ==7762==ERROR: LeakSanitizer: detected memory leaks != ~
> [  124s]                                       != ~
> [  124s] Indirect leak of 216 byte(s) in 1 object(s) allocated from: != ~
> [  124s]     #0 0x7f94b5001c4a in malloc (/usr/lib64/libasan.so.2+0x96c4a) != ~
> [  124s]     #1 0x7f94b4d610bc in __acl_init_obj (/home/abuild/rpmbuild/BUILD/acl-2.2.52/libacl/.libs/libacl.so.1+0x70bc) != ~
> [  124s]                                       != ~
> [  124s] Indirect leak of 56 byte(s) in 1 object(s) allocated from: != ~
> [  124s]     #0 0x7f94b5001c4a in malloc (/usr/lib64/libasan.so.2+0x96c4a) != ~
> [  124s]     #1 0x7f94b4d6423a in __new_var_obj_p (/home/abuild/rpmbuild/BUILD/acl-2.2.52/libacl/.libs/libacl.so.1+0xa23a) != ~
> [  124s]                                       != ~
> [  124s] SUMMARY: AddressSanitizer: 272 byte(s) leaked in 2 allocation(s). != ~

This is probably a minor concern, but maybe the above makes sense to fix?

Our bug: https://bugzilla.suse.com/show_bug.cgi?id=929108