https://bugs.openldap.org/show_bug.cgi?id=9942
Issue ID: 9942
Summary: back-mdb fails to release Added entries
Product: OpenLDAP
Version: 2.5.12
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: backends
Assignee: bugs(a)openldap.org
Reporter: hyc(a)openldap.org
Target Milestone: ---
Detected by valgrind on test002.
Appears to be a regression since some time after ITS#7915.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9895
Issue ID: 9895
Summary: Increase max number of index DBs in back-mdb
Product: OpenLDAP
Version: 2.5.12
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: backends
Assignee: bugs(a)openldap.org
Reporter: hyc(a)openldap.org
Target Milestone: ---
Currently there is a hardcoded limit of 128 index DBs in back-mdb. Some sites
want more than this (although there's no evidence they actually use more than
128 attributes in all of their applications' search filters).
For 2.5/2.6 we can simply double the constant. For 2.7 consider making it
configurable.
Note that increasing the number increases the size of an LMDB transaction
structure, and also increases the time needed to initialize it whenever
creating a transaction, so it's a bad idea to just set this to an arbitrarily
large number.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10006
Issue ID: 10006
Summary: gitlab account awaiting approval
Product: website
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: website
Assignee: bugs(a)openldap.org
Reporter: facboy(a)gmail.com
Target Milestone: ---
i've tried creating an account on https://git.openldap.org a few weeks ago, but
it is still awaiting approval. it has the same email as this bugzilla account.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10005
Issue ID: 10005
Summary: Fix flags not getting committed when using named dbs
in lmdb
Product: LMDB
Version: 0.9.29
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: liblmdb
Assignee: bugs(a)openldap.org
Reporter: mega.alpha100(a)gmail.com
Target Milestone: ---
This addition is simply a replication of some logic already in lmdb's repo to
ensure flags
are saved when using named db, like is already done for the main/unamed db
This is a link to the requested fix
https://github.com/Ultra-Code/lmdb/commit/ce001a311d8fb16afbf13df2a1e21d505…
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10002
Issue ID: 10002
Summary: Potential memory leak in tests/progs/slapd-bind.c
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: test suite
Assignee: bugs(a)openldap.org
Reporter: 1061499390(a)qq.com
Target Milestone: ---
Version: Github:master
Potential memory leak in slapd-bind.c line 139.Calling ldap_url_parse() without
calling ldap_free_urldesc() to free the memory will cause a memory leak.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10001
Issue ID: 10001
Summary: Potential memory leak in libraries/libldap/urltest.c
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: libraries
Assignee: bugs(a)openldap.org
Reporter: 1061499390(a)qq.com
Target Milestone: ---
Version: Github:master
Potential memory leak in urltest.c line 75.Calling ldap_url_parse() without
calling ldap_free_urldesc() to free the memory will cause a memory leak.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9994
Issue ID: 9994
Summary: Potential memory leak in tests/progs/slapd-modify.c
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: test suite
Assignee: bugs(a)openldap.org
Reporter: 1061499390(a)qq.com
Target Milestone: ---
Version: Github:master
Potential memory leak in slapd-modify.c line 164 and 191.Calling
ldap_modify_ext_s() without calling ldap_mods_free() to free the memory will
cause a memory leak.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9992
Issue ID: 9992
Summary: Requesting information about libraries/ldap_r
Product: OpenLDAP
Version: 2.5.12
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: libraries
Assignee: bugs(a)openldap.org
Reporter: jjrobert(a)lexmark.com
Target Milestone: ---
Apologies if this is a duplicate - the tracking system seemed to glitch when I
submitted so I'm typing it up again.
We are upgrading our stack from using openldap 2.4.57 to 2.5.12 and one of our
dependencies is missing lldap_r.
I searched and only really found this, which gives me some idea of its purpose:
https://marc.info/?l=openldap-devel&m=95218635611825
Is it simply gone now, or does it exist as a separate library?
Is there any guidance on what to do if you were using it previously?
Thanks,
-Jeff
--
You are receiving this mail because:
You are on the CC list for the issue.