[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: ldapadd with undefined objectclass causes assertion failure (ITS#3097)

In looking at the code, I think the main problem is
objectSubClassMatch returning SLAPD_COMPARE_UNDEFINED
instead of an LDAP result code, such as LDAP_INVALID_SYNTAX.

But also I think calling code needs to be tweaked as well.
I've committed changes to HEAD which should properly address
this issue.  Please test.


At 09:40 AM 4/19/2004, rhafer@suse.de wrote:
>Full_Name: Ralf Haferkamp
>Version: 2.2.10 (HEAD)
>OS: Linux
>URL: ftp://ftp.openldap.org/incoming/
>Submission from: (NULL) (
>When trying to add an entry with an undefined objectclass I get:
>slapd: result.c:556: slap_send_ldap_result: Assertion `!((rs->sr_err)<0)'
>Example entry:
>dn: dc=my-domain,dc=com
>objectclass: dcobject
>objectclass: undefined
>dc: my-domain
>If I see it correctly this bug was introduced with the fix for ITS#3066.
>value_match() called from server/slapd/modify.c (slap_mods_check()) line #799
>calls objectSubClassMatch() which then returns  SLAPD_COMPARE_UNDEFINED (-1)
>because of the undefined objectclass "undefined".