A talloc context is not freed during the PAC verification process. This creates an important memory leak:
talloc
==1668017== 1,161,407,680 (91,690,080 direct, 1,069,717,600 indirect) bytes in 955,105 blocks are definitely lost in loss record 66 of 66 ==1668017== at 0x484482F: malloc (vg_replace_malloc.c:431) ==1668017== by 0x551C0EF: __talloc_with_prefix (talloc.c:783) ==1668017== by 0x551C35D: UnknownInlinedFun (talloc.c:825) ==1668017== by 0x551C35D: UnknownInlinedFun (talloc.c:982) ==1668017== by 0x551C35D: talloc_named_const (talloc.c:1751) ==1668017== by 0x489AD12: ipadb_common_verify_pac.constprop.0 (ipa_kdb_mspac.c:2401) ==1668017== by 0x489B89F: ipadb_v9_issue_pac (ipa_kdb_mspac_v9.c:124) ==1668017== by 0x124E09: UnknownInlinedFun (kdc_authdata.c:507) ==1668017== by 0x124E09: handle_authdata (kdc_authdata.c:623) ==1668017== by 0x116B60: tgs_issue_ticket (do_tgs_req.c:1038) ==1668017== by 0x11E3FD: UnknownInlinedFun (do_tgs_req.c:1196) ==1668017== by 0x11E3FD: dispatch (dispatch.c:163) ==1668017== by 0x123B43: process_tcp_connection_read (net-server.c:1362) ==1668017== by 0x4A027FB: verto_fire (in /usr/lib64/libverto.so.1.0.0) ==1668017== by 0x8D91D82: ev_invoke_pending (in /usr/lib64/libev.so.4.0.0) ==1668017== by 0x8D9582F: ev_run (in /usr/lib64/libev.so.4.0.0)
This leak was introduced by commit 0022bd7.
Metadata Update from @jrische: - Custom field rhbz adjusted to RHEL-17996
Metadata Update from @jrische: - Custom field rhbz adjusted to RHEL-17996, RHEL-22644 (was: RHEL-17996)
master:
ipa-4-11:
ipa-4-10:
ipa-4-9:
Metadata Update from @frenaud: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.