[Date Prev][Date Next]
Re: (ITS#8434) Config entry cleanup on Add should be run unconditionally
- To: openldap-its@OpenLDAP.org
- Subject: Re: (ITS#8434) Config entry cleanup on Add should be run unconditionally
- From: email@example.com
- Date: Sat, 18 Jun 2016 20:34:11 +0000
- Auto-submitted: auto-generated (OpenLDAP-ITS)
On Wed, Jun 08, 2016 at 10:15:13PM +0000, firstname.lastname@example.org wrote:
> email@example.com wrote:
>> With cn=config the ConfigLDAPadd function might have to allocate resources that
>> are needed by the time the attributes/config directives are being processed
>> since there is no indication which directives there are and what order they come
> When using LDAPAdd, attributes are processed in the order of their schema
>> If any of the config values fail validation, the configuration code has to react
>> and clean up - which is possible using ca->cleanup.
> No, that's not its purpose. If anything fails, the entire config entry must be
> wiped out. LDAPAdd is all-or-nothing.
Yes, but the resource usually has to be allocated before the any of the
attributes are processed. In case of failure, the overlay does not have
a chance to react and free it since it has no idea when the reversal of
all of the attributes has finished.