#50857 Memory leak in ACI using IP subject
Closed: wontfix 7 months ago by tbordaz. Opened 8 months ago by tbordaz.

Issue Description

The leak is detected with ASAN build running dirsrvtests/tests/suites/acl/keywords_*

Package Version and Platform

All versions

Steps to reproduce

  1. install ASAN build
  2. run dirsrvtests/tests/suites/acl/keywords_*

Actual results

==13615==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 88 byte(s) in 1 object(s) allocated from:
    #0 0x7f53ae6ecb78 in __interceptor_malloc (/lib64/libasan.so.5+0xefb78)
    #1 0x7f539f36783e in INTsystem_malloc_perm (/usr/lib64/dirsrv/libns-dshttpd-
    #2 0x7f539f350563 in LASIpTreeAllocNode lib/libaccess/lasip.cpp:181
    #3 0x7f539f3520fb in LASIpAddPatternIPv6 lib/libaccess/lasip.cpp:649
    #4 0x7f539f3520fb in LASIpBuild lib/libaccess/lasip.cpp:335
    #5 0x7f539f3520fb in LASIpEval lib/libaccess/lasip.cpp:531
    #6 0x7f539f3556d5 in ACLEvalAce(NSErr_s*, ACLEvalHandle*, ACLExprHandle*, unsigned long*, PListStruct_s**, PListStruct_s*) lib/libaccess/oneeval.cpp:215
    #7 0x7f539f357400 in ACL_INTEvalTestRights lib/libaccess/oneeval.cpp:752
    #8 0x7f539f35852d in ACL_EvalTestRights (/usr/lib64/dirsrv/libns-dshttpd-
    #9 0x7f539f5c7e81 in acl__TestRights ldap/servers/plugins/acl/acl.c:3289
    #10 0x7f539f5d14ce in acl_access_allowed (/usr/lib64/dirsrv/plugins/libacl-plugin.so+0x224ce)
    #11 0x7f539f6049bb in acl_access_allowed_main ldap/servers/plugins/acl/aclplugin.c:371
    #12 0x7f53ae24ffea in plugin_call_acl_plugin (/usr/lib64/dirsrv/libslapd.so.0+0x1c3fea)
    #13 0x7f53ae250d7d in slapi_access_allowed (/usr/lib64/dirsrv/libslapd.so.0+0x1c4d7d)
    #14 0x7f539f5d4859 in acl_check_mods (/usr/lib64/dirsrv/plugins/libacl-plugin.so+0x25859)
    #15 0x7f53ae250252 in plugin_call_acl_mods_access (/usr/lib64/dirsrv/libslapd.so.0+0x1c4252)
    #16 0x7f539bc01f0e in ldbm_back_modify ldap/servers/slapd/back-ldbm/ldbm_modify.c:616
    #17 0x7f53ae20aa53 in op_shared_modify ldap/servers/slapd/modify.c:1021
    #18 0x7f53ae20ea0b in do_modify (/usr/lib64/dirsrv/libslapd.so.0+0x182a0b)
    #19 0x56130fb60e3d in connection_dispatch_operation ldap/servers/slapd/connection.c:638
    #20 0x56130fb60e3d in connection_threadmain ldap/servers/slapd/connection.c:1767
    #21 0x7f53aba54567  (/lib64/libnspr4.so+0x2b567)

Expected results

Should not leak

Metadata Update from @tbordaz:
- Issue assigned to tbordaz

8 months ago

Metadata Update from @tbordaz:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None

8 months ago

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.3.10

8 months ago

Metadata Update from @tbordaz:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1796558

8 months ago

8d6f8f5..583c9b3 389-ds-base-1.4.2
2a62015..a19f0c0 389-ds-base-1.4.1
9fd5623..7fbd4b6 389-ds-base-1.4.0
7abd73c..f58f732 389-ds-base-1.3.10

Metadata Update from @tbordaz:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

7 months ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/3911

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: fixed)

16 days ago

Login to comment on this ticket.