Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 796448 [details]
Reproducer script

Running the attached script, the OpenLMI Account provider leaks memory:

==24551== 121,915 (9,184 direct, 112,731 indirect) bytes in 28 blocks are definitely lost in loss record 387 of 387
==24551==    at 0x4C29121: calloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==24551==    by 0xE4C1EC6: g_malloc0 (in /usr/lib64/libglib-2.0.so.0.3707.0)
==24551==    by 0x1032E0C1: libuser_files_init (in /usr/lib64/libuser/libuser_files.so)
==24551==    by 0xE7AE229: ??? (in /usr/lib64/libuser.so.1.4.1)
==24551==    by 0xE7B07A7: lu_start (in /usr/lib64/libuser.so.1.4.1)
==24551==    by 0xDE59968: ???
==24551==    by 0xE26DF3C: ???
==24551==    by 0xDE5969B: ???
==24551==    by 0xDBEFCBA: ???
==24551==    by 0xDBFD1C4: ???
==24551==    by 0x7F3D369: Pegasus::BasicProviderManagerRouter::processMessage(Pegasus::Message*) (BasicProviderManagerRouter.cpp:391)
==24551==    by 0x7D2DDE0: Pegasus::ProviderManagerService::_processMessage(Pegasus::CIMRequestMessage*) (ProviderManagerService.cpp:870)

Tested with current upstream git head, 8dbd4f1f39c66309806642532635de2a764fa738

(I *do* have openlmi-providers-debuginfo installed, how can I get better stack traces in valgrind?)

This is either fixed upstream or I can't reproduce it any longer.

I have gone through the source code manually as a part of fixing libuser objects cleanup but haven't found a place with obvious leak.

(In reply to Jan Safranek from comment #0)
> ==24551==    by 0xE7B07A7: lu_start (in /usr/lib64/libuser.so.1.4.1)

In case this happens again, a location of the incidental lu_start() call would be a great help.