New subject: [Issue 10219] Modify of olcDisabled by removing and adding a value invokes db_open twice

23 May 2024


      https://bugs.openldap.org/show_bug.cgi?id=10219
Issue ID: 10219
           Summary: Modify of olcDisabled by removing and adding a value
                    invokes db_open twice
           Product: OpenLDAP
           Version: 2.6.7
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Keywords: needs_review
          Severity: normal
          Priority: ---
         Component: slapd
          Assignee: bugs@openldap.org
          Reporter: nivanova@symas.com
  Target Milestone: ---
A database is enabled by default, and therefore a missing olcDisabled attribute
is equivalent to a value of FALSE. This means that currently a modify operation
that removes a olcDisabled value will invoke the db_open handler for that
database, even if in the same modify operation a value of TRUE is added.
A modify operation like this:
dn: olcDatabase={1}asyncmeta,cn=config
changetype: modify
delete: olcDisabled
olcDisabled: FALSE
-
add: olcDisabled
olcDisabled: TRUE
-
will call both db_open and db_close. This could be potentially harmful if the
backend type allocates memory on db_open like asyncmeta, for example. It is a
rare case, but it is best to fix it just in case.
-- 
You are receiving this mail because:
You are on the CC list for the issue.

[Issue 10219] New: Modify of olcDisabled by removing and adding a value invokes db_open twice