- openldap-bugs - openldap.org

Re: (ITS#7418) slapo-constraint are broken
by michael＠stroeder.com 18 Oct '12

18 Oct '12

This is a cryptographically signed message in MIME format. --------------ms060905030203070305090206 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I suspect this is related to changes because of fix for ITS#7168 similar or same like ITS#7340. Ciao, Michael. --------------ms060905030203070305090206 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIILHzCC BT8wggQnoAMCAQICDwCmSwABAAIAivjZQ8SBvzANBgkqhkiG9w0BAQUFADB8MQswCQYDVQQG EwJERTEcMBoGA1UEChMTVEMgVHJ1c3RDZW50ZXIgR21iSDElMCMGA1UECxMcVEMgVHJ1c3RD ZW50ZXIgQ2xhc3MgMSBMMSBDQTEoMCYGA1UEAxMfVEMgVHJ1c3RDZW50ZXIgQ2xhc3MgMSBM MSBDQSBJWDAeFw0xMjA2MDYxOTAyMTZaFw0xMzA2MDcxOTAyMTZaMCgxCzAJBgNVBAYTAkRF MRkwFwYDVQQDDBBNaWNoYWVsIFN0csO2ZGVyMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB CgKCAQEAxXZGav40rnGNLxEggBW94MILWHlfC8a23Jew5U1gPlfRTXOjjzmoaZ1uCyGdgF6M VvuO9T1aTQNGH+OdeGe3P7Tfc/NsLJFJ2wtd8blvhmodUgse2eypiWjNOd4gZuhalBhgsQ0K b5D6/1foghII4E264iZlJ7AJ+UYcO+GxvFWT0YMTbLckgDkZk7c3qwTozdhYvXarvqx+8Ou/ kuxpQQhac/ebzxpu0N+RHSf2KIUS0g0tEGnPtGv6iL+9QNHc4JKo9Y9KKVw3tQy+Re+FQLxB 1fPE5F+qxuD3AUENpOwkMsqWLM94ohtx3CFqLpxfUPrnKFLAHOhHEbByYGvFPwIDAQABo4IC EDCCAgwwgaUGCCsGAQUFBwEBBIGYMIGVMFEGCCsGAQUFBzAChkVodHRwOi8vd3d3LnRydXN0 Y2VudGVyLmRlL2NlcnRzZXJ2aWNlcy9jYWNlcnRzL3RjX2NsYXNzMV9MMV9DQV9JWC5jcnQw QAYIKwYBBQUHMAGGNGh0dHA6Ly9vY3NwLml4LnRjY2xhc3MxLnRjdW5pdmVyc2FsLWkudHJ1 c3RjZW50ZXIuZGUwHwYDVR0jBBgwFoAU6bgoHUbP/M34TpvF7ktg69g7P9EwDAYDVR0TAQH/ BAIwADBKBgNVHSAEQzBBMD8GCSqCFAAsAQEBATAyMDAGCCsGAQUFBwIBFiRodHRwOi8vd3d3 LnRydXN0Y2VudGVyLmRlL2d1aWRlbGluZXMwDgYDVR0PAQH/BAQDAgTwMB0GA1UdDgQWBBS2 KAWfTfgJ/JQ63qLGwTXYLnI+LzBiBgNVHR8EWzBZMFegVaBThlFodHRwOi8vY3JsLml4LnRj Y2xhc3MxLnRjdW5pdmVyc2FsLWkudHJ1c3RjZW50ZXIuZGUvY3JsL3YyL3RjX0NsYXNzMV9M MV9DQV9JWC5jcmwwMwYDVR0lBCwwKgYIKwYBBQUHAwIGCCsGAQUFBwMEBggrBgEFBQcDBwYK KwYBBAGCNxQCAjAfBgNVHREEGDAWgRRtaWNoYWVsQHN0cm9lZGVyLmNvbTANBgkqhkiG9w0B AQUFAAOCAQEAQ3bvVUpEq+cQrLpcogyt5BJNk/WvUvOHqhzyj28M9pg9hcDl1+MYl5qqj6tR GSTLPQZyf287pcmbMwbcTGZO/gbW9v7RYcut6RauWdwKMCUmKC3J4fVfDq9ZETA2WOV68ef4 B3Gzdhghsbp3Rhp5dDmrCVKAHlafm6ZwJrEQ9P76fxnQZzRLgeKpZep5ePH5YHUB3+YaOQvJ FG0bOXvfHhRiRG7/HW2G+yDgjHSxDz8AFzMWL/RFePqZ4pn6T/SM/qU6WEpW39MWyJNoH/Kx QDYK8gGYuesn1ciMCTnjrvZQj0fonGTO4SfWekJRkuGrJ7dYSZRjYbDcWBBkdFLWzzCCBdgw ggTAoAMCAQICDgboAAEAAkqWLSQM/sXJMA0GCSqGSIb3DQEBBQUAMHkxCzAJBgNVBAYTAkRF MRwwGgYDVQQKExNUQyBUcnVzdENlbnRlciBHbWJIMSQwIgYDVQQLExtUQyBUcnVzdENlbnRl ciBVbml2ZXJzYWwgQ0ExJjAkBgNVBAMTHVRDIFRydXN0Q2VudGVyIFVuaXZlcnNhbCBDQSBJ MB4XDTA5MTEwMzE0MDgxOVoXDTI1MTIzMTIxNTk1OVowfDELMAkGA1UEBhMCREUxHDAaBgNV BAoTE1RDIFRydXN0Q2VudGVyIEdtYkgxJTAjBgNVBAsTHFRDIFRydXN0Q2VudGVyIENsYXNz IDEgTDEgQ0ExKDAmBgNVBAMTH1RDIFRydXN0Q2VudGVyIENsYXNzIDEgTDEgQ0EgSVgwggEi MA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC75pBuz2Lp6QuqthDVR+V8XSsncZpozVVt 5KLv5P7yemMRwleKyH3PjmYfZUVL64Biab1GjovFblqVGCrep/EfdRonq20yU+P7TVhiLP8Z 5cegDZotIYhZhM0d8cPIij6w5d4IJM/8QCy6QSOUu4ASiTVItoYE4AFPjLqpmPwcie0fiqHH hpgmHnJla/7PZdkMZEsaCfVDEWBmJuMzVprJPT40anjG5VBLyM2I5DlsUCaeQCy2O3w3sqf1 3dyzUcv03IICuNc63towXA31Qt0TaVNU6YAmQjMepdfMbspmCZ+G8D2+xophEPPR/1vkstst smUMqX0XrLonTUJczglPAgMBAAGjggJZMIICVTCBmgYIKwYBBQUHAQEEgY0wgYowUgYIKwYB BQUHMAKGRmh0dHA6Ly93d3cudHJ1c3RjZW50ZXIuZGUvY2VydHNlcnZpY2VzL2NhY2VydHMv dGNfdW5pdmVyc2FsX3Jvb3RfSS5jcnQwNAYIKwYBBQUHMAGGKGh0dHA6Ly9vY3NwLnRjdW5p dmVyc2FsLUkudHJ1c3RjZW50ZXIuZGUwHwYDVR0jBBgwFoAUkqR1LKSevoFE63n8isWVpesQ dXMwEgYDVR0TAQH/BAgwBgEB/wIBADBSBgNVHSAESzBJMAYGBFUdIAAwPwYJKoIUACwBAQEB MDIwMAYIKwYBBQUHAgEWJGh0dHA6Ly93d3cudHJ1c3RjZW50ZXIuZGUvZ3VpZGVsaW5lczAO BgNVHQ8BAf8EBAMCAQYwHQYDVR0OBBYEFOm4KB1Gz/zN+E6bxe5LYOvYOz/RMIH9BgNVHR8E gfUwgfIwge+ggeyggemGRmh0dHA6Ly9jcmwudGN1bml2ZXJzYWwtSS50cnVzdGNlbnRlci5k ZS9jcmwvdjIvdGNfdW5pdmVyc2FsX3Jvb3RfSS5jcmyGgZ5sZGFwOi8vd3d3LnRydXN0Y2Vu dGVyLmRlL0NOPVRDJTIwVHJ1c3RDZW50ZXIlMjBVbml2ZXJzYWwlMjBDQSUyMEksTz1UQyUy MFRydXN0Q2VudGVyJTIwR21iSCxPVT1yb290Y2VydHMsREM9dHJ1c3RjZW50ZXIsREM9ZGU/ Y2VydGlmaWNhdGVSZXZvY2F0aW9uTGlzdD9iYXNlPzANBgkqhkiG9w0BAQUFAAOCAQEAOcjE m+6+mO5Icm+N53G2DpCM07LBFSGoRpBoX0oE8TrJaIQh2KXmBHVdn9LU8kt3QzLclctgvwJV 0KwcsMUUl5tlCsMPpR3s2Ek5lbWpvvr0HqtW56blAQiINV9nBd1EJFASIkRjefGbV2nOq9Yz UU+N8HA7jq1ROhd/NZZraGhjthwKyfjfHV7PKxGlY+3M0MbTIG+q/GhIfm0euDpFqhKG88e9 ALXr/uoSn3MzeOcoOWjTpW3adtFO4VWVgKbgG7jNrFbvRVlHmFLbOm4msjE5aXWxLiTwpJ2X iF4zKca1vAdAOgw9us90jEtOeiH6GzjNxEMvb7TfeO6Zkuc6HDGCA84wggPKAgEBMIGPMHwx CzAJBgNVBAYTAkRFMRwwGgYDVQQKExNUQyBUcnVzdENlbnRlciBHbWJIMSUwIwYDVQQLExxU QyBUcnVzdENlbnRlciBDbGFzcyAxIEwxIENBMSgwJgYDVQQDEx9UQyBUcnVzdENlbnRlciBD bGFzcyAxIEwxIENBIElYAg8ApksAAQACAIr42UPEgb8wCQYFKw4DAhoFAKCCAhMwGAYJKoZI hvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTIxMDE4MTkyNjAyWjAjBgkq hkiG9w0BCQQxFgQU7QCgPPclKaMhoNwC33a+he0n9jAwbAYJKoZIhvcNAQkPMV8wXTALBglg hkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggq hkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBoAYJKwYBBAGCNxAEMYGSMIGP MHwxCzAJBgNVBAYTAkRFMRwwGgYDVQQKExNUQyBUcnVzdENlbnRlciBHbWJIMSUwIwYDVQQL ExxUQyBUcnVzdENlbnRlciBDbGFzcyAxIEwxIENBMSgwJgYDVQQDEx9UQyBUcnVzdENlbnRl ciBDbGFzcyAxIEwxIENBIElYAg8ApksAAQACAIr42UPEgb8wgaIGCyqGSIb3DQEJEAILMYGS oIGPMHwxCzAJBgNVBAYTAkRFMRwwGgYDVQQKExNUQyBUcnVzdENlbnRlciBHbWJIMSUwIwYD VQQLExxUQyBUcnVzdENlbnRlciBDbGFzcyAxIEwxIENBMSgwJgYDVQQDEx9UQyBUcnVzdENl bnRlciBDbGFzcyAxIEwxIENBIElYAg8ApksAAQACAIr42UPEgb8wDQYJKoZIhvcNAQEBBQAE ggEAYODTh49NYBcdsAkvO9kTYc/VjSVJrTgQbiau0T8JPupHvjrFuHTFfrKRUSrw3gVYR9Fq DhLx/lw0yM6Ced86B7v/GVMjAo4hEE/UV41hCvSd4WXn5DsDRTNQFX3YCSNpTb8fQALJDcRw SL1IRMbGnZdVDHIQGtZ+WR9+0yKLn1m/Bitgh25pZJhdbW+QaRNCEKFuUuqM039BzvVIy+3I yihMjC64xY4dIJplhoedtCJ8JzJaHJgOoetrgcJBkDPmNb0yEA7mjZCEyu+BBizstu5886j/ AygwwHn6NB+Av7Dz2SIl2sOmN0BsPIA2Yu2htDOZqDQjtGfh0LRDenyyBAAAAAAAAA== --------------ms060905030203070305090206--

1 0

(ITS#7418) slapo-constraint are broken
by sascha.kuehndel＠deka.de 18 Oct '12

18 Oct '12

Full_Name: Sascha Kuehndel Version: 2.4.33 OS: HP-UX 11.31 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (192.166.104.102) After upgrade slapd from 2.4.32 to 2.4.33, same contraints fails always. Any change on an entry in restricted tree is not possible. 1. Comment out the contraints helps. 2. I have downgraded the constraint.c, only. After rebuild, the slapds works fine again. Constraint: constraint_attribute dekanetZielgruppenDN uri ldap:///ou=Zielgruppen,ou=dekanet,dc=dekager,dc=dekabank,dc=extern?entryDN?one?(objectClass=dekanetZielgruppe) restrict=ldap:///ou=Benutzer,ou=dekanet,dc=dekager,dc=dekabank,dc=extern??one Change: #!RESULT ERROR #!CONNECTION ldap://dk-ketos:6418 #!DATE 2012-10-18T18:29:02.840 #!ERROR [LDAP: error code 19 - modify breaks constraint on dekanetEmailAdr] dn: dekanetObjLID=74386878,ou=Benutzer,ou=dekanet,dc=dekager,dc=dekabank,dc=ex tern changetype: modify replace: dekanetEmailAdr dekanetEmailAdr: test1234(a)deka.de - Greatings, Sascha

1 0

Re: (ITS#7417) Why is there no schema add utility?
by jerrac＠gmail.com 17 Oct '12

17 Oct '12

--f46d04447dffae07bd04cc34c745 Content-Type: text/plain; charset=ISO-8859-1 Really? How? Also, the method described by Zytrax is pretty much what all the search results said. Including https://help.ubuntu.com/12.04/serverguide/openldap-server.html And I couldn't find anything different in the Openldap.org documentation. Again, maybe because I didn't search for the right things... With slapadd and ldapadd, can you add a .schema file? Or does it have to be in LDIF syntax? *goes to check the man page* --David Reagan On Tue, Oct 16, 2012 at 1:31 PM, Howard Chu <hyc(a)symas.com> wrote: > jerrac(a)gmail.com wrote: > >> Full_Name: David Reagan >> Version: 2.4 >> OS: Ubuntu 12.04 >> URL: ftp://ftp.openldap.org/**incoming/<ftp://ftp.openldap.org/incoming/> >> Submission from: (NULL) (163.41.112.5) >> >> >> Why is there no simple way to add new schema's to cn=Config? As in, >> something >> like "slapadd --schema newschema.schema". >> > > Eh? New schemas can be added directly using slapadd, or using ldapadd. > > The best explanation I found on how to add a new schema is >> http://www.zytrax.com/books/**ldap/ch6/slapd-config.html#**use-schemas<http://www.zytrax.com/books/ldap/ch6/slapd-config.html#use-schemas>. >> You have to >> create a conf file, a new directory, run a command, edit a file, and then >> run >> another command. That's a lot of places where user error could break >> things. >> > > Your first mistake is in trusting anything that Zytrax says. Most of their > information is out of date or flat wrong. > > -- > -- Howard Chu > CTO, Symas Corp. http://www.symas.com > Director, Highland Sun http://highlandsun.com/hyc/ > Chief Architect, OpenLDAP http://www.openldap.org/**project/<http://www.openldap.org/project/> > --f46d04447dffae07bd04cc34c745 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Really? How? Also, the method described by Zytrax is pretty much wh= at all the search results said. Including <a href=3D"https://help.ubuntu.co= m/12.04/serverguide/openldap-server.html">https://help.ubuntu.com/12.04/ser= verguide/openldap-server.html</a> And I couldn't find anything different in the Openldap.org document= ation. Again, maybe because I didn't search for the right things... = With slapadd and ldapadd, can you add a .schema file? Or does it have t= o be in LDIF syntax? *goes to check the man page* --David Reagan <div class=3D"gmail_quote">On Tue, Oct 16, 2012 at 1:31 PM, Howard = Chu <<a href=3D"mailto:hyc@symas.com" target=3D"_blank= ">hyc(a)symas.com</a>> wrote: <blockquote class=3D"gmail_quote" = style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <a href=3D"mailto:jerrac@gmail.com" target=3D"_blank">jerrac(a)gmail.com</a> = wrote: <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"> Full_Name: David Reagan Version: 2.4 OS: Ubuntu 12.04 URL: <a href=3D"ftp://ftp.openldap.org/incoming/" target=3D"_blank">ftp://f= tp.openldap.org/incoming/</a> Submission from: (NULL) (163.41.112.5) Why is there no simple way to add new schema's to cn=3DConfig? As in, s= omething like "slapadd --schema newschema.schema". </blockquote> Eh? New schemas can be added directly using slapadd, or using ldapadd. <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"> The best explanation I found on how to add a new schema is <a href=3D"http://www.zytrax.com/books/ldap/ch6/slapd-config.html#use-schem= as" target=3D"_blank">http://www.zytrax.com/books/ldap/ch6/slapd-con= fig.html#use-schemas</a>. You have to create a conf file, a new directory, run a command, edit a file, and then r= un another command. That's a lot of places where user error could break th= ings. </blockquote> Your first mistake is in trusting anything that Zytrax says. Most of their = information is out of date or flat wrong. -- =A0 -- Howard Chu =A0 CTO, Symas Corp. =A0 =A0 =A0 =A0 =A0 <a href=3D"http://www.symas.com" t= arget=3D"_blank">http://www.symas.com</a> =A0 Director, Highland Sun =A0 =A0 <a href=3D"http://highlandsun.com/hyc/" = target=3D"_blank">http://highlandsun.com/hyc/</a> =A0 Chief Architect, OpenLDAP =A0<a href=3D"http://www.openldap.org/project= /" target=3D"_blank">http://www.openldap.org/project/</a> </blockquote></div> --f46d04447dffae07bd04cc34c745--

1 0

Re: (ITS#7417) Why is there no schema add utility?
by hyc＠symas.com 16 Oct '12

16 Oct '12

jerrac(a)gmail.com wrote: > Full_Name: David Reagan > Version: 2.4 > OS: Ubuntu 12.04 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (163.41.112.5) > > > Why is there no simple way to add new schema's to cn=Config? As in, something > like "slapadd --schema newschema.schema". Eh? New schemas can be added directly using slapadd, or using ldapadd. > The best explanation I found on how to add a new schema is > http://www.zytrax.com/books/ldap/ch6/slapd-config.html#use-schemas. You have to > create a conf file, a new directory, run a command, edit a file, and then run > another command. That's a lot of places where user error could break things. Your first mistake is in trusting anything that Zytrax says. Most of their information is out of date or flat wrong. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

(ITS#7417) Why is there no schema add utility?
by jerrac＠gmail.com 16 Oct '12

16 Oct '12

Full_Name: David Reagan Version: 2.4 OS: Ubuntu 12.04 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (163.41.112.5) Why is there no simple way to add new schema's to cn=Config? As in, something like "slapadd --schema newschema.schema". The best explanation I found on how to add a new schema is http://www.zytrax.com/books/ldap/ch6/slapd-config.html#use-schemas. You have to create a conf file, a new directory, run a command, edit a file, and then run another command. That's a lot of places where user error could break things. So, is there a utility in the works, or are there other reasons this would be a bad idea? I'm curious. I did search Google, the tickets, and the mailing lists. But either there isn't anything there, or my search terms were bad. If this has already be discussed, I apologize for bringing it up again, and would appreciate a link to the discussion.

1 0

Re: (ITS#7415) Add MALLOC_CHECK_ and MALLOC_PERTURB_ libc env to the test suite for detecting heap corruption
by hyc＠symas.com 12 Oct '12

12 Oct '12

Kurt(a)OpenLDAP.org wrote: > You miss the fact that we encourage deployers of OpenLDAP Software, who we recommend build OpenLDAP Software from source, run 'make test' before they 'make install'. We don't want these deployers to have false positives, such as would be likely caused if we added such environmental variables. > > For those doing automated checks, such as those who do construct packages, they can have local patches to their hearts content. Likewise for developers. > > So, if it was up to me, I would reject your patch as, IMO, it's in appropriate for our source distributions. I suspect Howard will chime in sooner or later. I think you've already covered the points. I have plenty of checks like this in my local source tree, but I see no reason to embed OS and platform-specific stuff into the distributed source. I believe it would lend a false sense of security, particularly when you're on a platform that ignores these variables, but you aren't aware of the fact. It is always the developers' responsibility to know how their own development environment works, and to tweak it to suit their development efforts. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#7415) Add MALLOC_CHECK_ and MALLOC_PERTURB_ libc env to the test suite for detecting heap corruption
by gitter.spiros＠gmail.com 12 Oct '12

12 Oct '12

2012/10/12 Kurt Zeilenga <Kurt(a)openldap.org>: > > On Oct 12, 2012, at 8:38 AM, Elia Pinto <gitter.spiros(a)gmail.com> wrote: > >> 2012/10/12 Kurt Zeilenga <Kurt(a)openldap.org>: >>> You miss the fact that we encourage deployers of OpenLDAP Software, who we recommend build OpenLDAP Software from source, run 'make test' before they 'make install'. We don't want these deployers to have false positives, such as would be likely caused if we added such environmental variables. >> >> It is your own opinion, right? Have experiences in this regard? > > Yes and Yes. I use to run with such environmental variables set in my .login. Not anymore, too many odd crashes. So sometimes I do something like: > env MallocScribble=yes MallocErrorAbort=yes make test > > but I've that crash above and below the run script, but not in OpenLDAP Software itself. So now, because I tend to run stuff I'm working on in a debugger, I now mostly rely on my debugger to turn malloc debugging on. And I tend to use other tools for leak detection (like leaks(1) on MacOS/X). HeHe, i suspect was ONLY a MacOS/X crap. Good to know. > > -- Kurt > > >> I do >> not. I personally run make test on openldap with Ubuntu 4.12, Fedora >> 17 and RHEL6 and my patch without any problem (good for openldap :=) >> ). And many other projects, for example, git hat has a very extensive >> test suite, use MALLOC_CHECK as in my patch, integrated in a test >> suite. >> >> However, I will not insist further on a trivial patch. Also because >> this discussion gave me the opportunity to investigate better the >> issue, and I'll just patch for FreeBSD my software. So, thank you >> anyway for the useful observations. >> >> Regards >>> >>> For those doing automated checks, such as those who do construct packages, they can have local patches to their hearts content. Likewise for developers. >>> >>> So, if it was up to me, I would reject your patch as, IMO, it's in appropriate for our source distributions. I suspect Howard will chime in sooner or later. >>> >>> -- Kurt >>> >

1 0

Re: (ITS#7415) Add MALLOC_CHECK_ and MALLOC_PERTURB_ libc env to the test suite for detecting heap corruption
by Kurt＠OpenLDAP.org 12 Oct '12

12 Oct '12

On Oct 12, 2012, at 8:38 AM, Elia Pinto <gitter.spiros(a)gmail.com> wrote: > 2012/10/12 Kurt Zeilenga <Kurt(a)openldap.org>: >> You miss the fact that we encourage deployers of OpenLDAP Software, who we recommend build OpenLDAP Software from source, run 'make test' before they 'make install'. We don't want these deployers to have false positives, such as would be likely caused if we added such environmental variables. > > It is your own opinion, right? Have experiences in this regard? Yes and Yes. I use to run with such environmental variables set in my .login. Not anymore, too many odd crashes. So sometimes I do something like: env MallocScribble=yes MallocErrorAbort=yes make test but I've that crash above and below the run script, but not in OpenLDAP Software itself. So now, because I tend to run stuff I'm working on in a debugger, I now mostly rely on my debugger to turn malloc debugging on. And I tend to use other tools for leak detection (like leaks(1) on MacOS/X). -- Kurt > I do > not. I personally run make test on openldap with Ubuntu 4.12, Fedora > 17 and RHEL6 and my patch without any problem (good for openldap :=) > ). And many other projects, for example, git hat has a very extensive > test suite, use MALLOC_CHECK as in my patch, integrated in a test > suite. > > However, I will not insist further on a trivial patch. Also because > this discussion gave me the opportunity to investigate better the > issue, and I'll just patch for FreeBSD my software. So, thank you > anyway for the useful observations. > > Regards >> >> For those doing automated checks, such as those who do construct packages, they can have local patches to their hearts content. Likewise for developers. >> >> So, if it was up to me, I would reject your patch as, IMO, it's in appropriate for our source distributions. I suspect Howard will chime in sooner or later. >> >> -- Kurt >>

1 0

Re: (ITS#7415) Add MALLOC_CHECK_ and MALLOC_PERTURB_ libc env to the test suite for detecting heap corruption
by gitter.spiros＠gmail.com 12 Oct '12

12 Oct '12

2012/10/12 Kurt Zeilenga <Kurt(a)openldap.org>: > You miss the fact that we encourage deployers of OpenLDAP Software, who we recommend build OpenLDAP Software from source, run 'make test' before they 'make install'. We don't want these deployers to have false positives, such as would be likely caused if we added such environmental variables. It is your own opinion, right? Have experiences in this regard? I do not. I personally run make test on openldap with Ubuntu 4.12, Fedora 17 and RHEL6 and my patch without any problem (good for openldap :=) ). And many other projects, for example, git hat has a very extensive test suite, use MALLOC_CHECK as in my patch, integrated in a test suite. However, I will not insist further on a trivial patch. Also because this discussion gave me the opportunity to investigate better the issue, and I'll just patch for FreeBSD my software. So, thank you anyway for the useful observations. Regards > > For those doing automated checks, such as those who do construct packages, they can have local patches to their hearts content. Likewise for developers. > > So, if it was up to me, I would reject your patch as, IMO, it's in appropriate for our source distributions. I suspect Howard will chime in sooner or later. > > -- Kurt >

1 0

Re: (ITS#7415) Add MALLOC_CHECK_ and MALLOC_PERTURB_ libc env to the test suite for detecting heap corruption
by Kurt＠OpenLDAP.org 12 Oct '12

12 Oct '12

You miss the fact that we encourage deployers of OpenLDAP Software, who we recommend build OpenLDAP Software from source, run 'make test' before they 'make install'. We don't want these deployers to have false positives, such as would be likely caused if we added such environmental variables. For those doing automated checks, such as those who do construct packages, they can have local patches to their hearts content. Likewise for developers. So, if it was up to me, I would reject your patch as, IMO, it's in appropriate for our source distributions. I suspect Howard will chime in sooner or later. -- Kurt

1 0

Re: (ITS#7415) Add MALLOC_CHECK_ and MALLOC_PERTURB_ libc env to the test suite for detecting heap corruption
by gitter.spiros＠gmail.com 12 Oct '12

12 Oct '12

2012/10/11 Kurt Zeilenga <Kurt(a)openldap.org>: > I note that these environment variables are specific to Linux, and then only certain Linux systems. If we add these, then we should also add similar environment variables for FreeBSD malloc(3), MacOS/X malloc(3), and various alternative malloc(3) libraries. And then we might get into cases where variables for one set of environmental variables conflict with another. As these can be set by the developer as desired in their development environment, there's little reason to get into setting all the malloc(3) environmental variables that might be useful... and we shouldn't play favors and only set variables for Linux. Sorry for the delay, problems to the my $DAYWORK Ok. First of all, elibc (debian/ubuntu recently) and glibc cover probably 95% of the Linux distributions, and they are compatible, in particular for the MALLOC_CHECK http://lwn.net/Articles/333755/ - i have also checked the source. A considerable part of the remaining operating systems are like BSD - FreeBSD for example - and MacOSX, FreeBSD based. In fact, these latter two have different malloc library and it may be necessary to activate different controls for different systems (see the first reference) http://permalink.gmane.org/gmane.network.openvswitch.devel/14838 http://www.unix.com/man-page/freebsd/5/malloc.conf/ But the benefits of automating these tests is to do a better AUTOQA for the buildsystem. It is also not true, as experience shows, that all developers know everything. Beeing expert in LDAP and C programming, for example, does not mean necessarily be an expert in everything: this can certainly be true for the OPENLDAP developers but it is not always the case. Here some examples: http://lists.fedoraproject.org/pipermail/devel/2010-May/135683.html (this check had found many bug that the upstream developer haven't catched) or this, from my mantainer, http://lists.gnupg.org/pipermail/gcrypt-devel/2010-June/001605.html I saw that you have closed the case(WANTFIX i think), however, I have to tell you better my opinion. If, as can happen, you decide that my reasons make sense, i can reroll my patch for Linux, macos and freebsd. Let me know. Thanks anyway for your reply > > -- Kurt >

1 0

Re: (ITS#7414) rwm: ldapmodify, slapd segmentation fault
by jvcelak＠redhat.com 12 Oct '12

12 Oct '12

> > The slapd daemon will crash, here is the full backtrace: > > Thanks for the detailed report. Fixed now in master. > Thank you for the very fast resolution. Jan

1 0

Re: (ITS#7415) Add MALLOC_CHECK_ and MALLOC_PERTURB_ libc env to the test suite for detecting heap corruption
by kurt＠OpenLDAP.org 12 Oct '12

12 Oct '12

On Oct 11, 2012, at 1:44 PM, h.b.furuseth(a)usit.uio.no wrote: > We can describe these and other variables in tests/README. There's lots of malloc variables one could describe. Better off to simply say that one might want to read the documentation for whatever malloc they are using, and use, if they want, any environmental variables they might want to use. This avoids duplicating detail better left to the malloc documentation. > > Yeah I know, people don't read documentation. The testing > announcements could mention the file though. Wrong audience, me thinks, especially if those announcements are posted to openldap-techncial. We don't need openldap users reporting malloc use issues in non-OpenLDAP programs. Use of such variables should be limited to developers. -- Kurt > >

1 0

(ITS#7416) entryCSN index errors when changing olcDbEnvFlags with back-mdb
by quanah＠OpenLDAP.org 11 Oct '12

11 Oct '12

Full_Name: Quanah Gibson-Mount Version: 2.4.33 OS: Linux 2.6 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (74.196.25.250) I found that if I modify the olcDbEnvFlags on a back-mdb database to have: olcDbEnvFlags: writemap olcDbEnvFlags: nometasync Then modifications in the primary database will throw the following error until slapd is restarted: Oct 11 14:38:01 zre-ldap002 slapd[22940]: conn=1001 fd=11 ACCEPT from PATH=/opt/zimbra/openldap-2.4.33.2z/var/run/ldapi (PATH=/opt/zimbra/openldap-2.4.33.2z/var/run/ldapi) Oct 11 14:38:01 zre-ldap002 slapd[22940]: conn=1001 op=0 BIND dn="cn=config" method=128 Oct 11 14:38:01 zre-ldap002 slapd[22940]: conn=1001 op=0 BIND dn="cn=config" mech=SIMPLE ssf=0 Oct 11 14:38:01 zre-ldap002 slapd[22940]: conn=1001 op=0 RESULT tag=97 err=0 text= Oct 11 14:38:01 zre-ldap002 slapd[22940]: conn=1001 op=1 SRCH base="cn=accesslog" scope=0 deref=2 filter="(objectClass=*)" Oct 11 14:38:01 zre-ldap002 slapd[22940]: conn=1001 op=1 SRCH attr=1.1 Oct 11 14:38:01 zre-ldap002 slapd[22940]: conn=1001 op=1 SEARCH RESULT tag=101 err=32 nentries=0 text= Oct 11 14:38:01 zre-ldap002 slapd[22940]: conn=1001 op=2 SRCH base="olcDatabase={2}mdb,cn=config" scope=0 deref=2 filter="(objectClass=*)" Oct 11 14:38:01 zre-ldap002 slapd[22940]: conn=1001 op=2 SRCH attr=olcDbEnvFlags Oct 11 14:38:01 zre-ldap002 slapd[22940]: conn=1001 op=2 SEARCH RESULT tag=101 err=0 nentries=1 text= Oct 11 14:38:01 zre-ldap002 slapd[22940]: conn=1001 op=3 MOD dn="olcDatabase={2}mdb,cn=config" Oct 11 14:38:01 zre-ldap002 slapd[22940]: conn=1001 op=3 MOD attr=olcDbEnvFlags Oct 11 14:38:01 zre-ldap002 slapd[22940]: slap_queue_csn: queing 0x7f88c17fc3f0 20121011213801.832254Z#000000#000#000000 Oct 11 14:38:01 zre-ldap002 slapd[22940]: conn=1001 op=3 RESULT tag=103 err=0 text= Oct 11 14:38:01 zre-ldap002 slapd[22940]: slap_graduate_commit_csn: removing 0x41d4690 20121011213801.832254Z#000000#000#000000 Oct 11 14:38:01 zre-ldap002 slapd[22940]: conn=1001 op=4 MOD dn="uid=zmpostfix,cn=appaccts,cn=zimbra" Oct 11 14:38:01 zre-ldap002 slapd[22940]: conn=1001 op=4 MOD attr=zimbraId Oct 11 14:38:01 zre-ldap002 slapd[22940]: slap_queue_csn: queing 0x7f88c17fd1a0 20121011213801.864697Z#000000#000#000000 Oct 11 14:38:01 zre-ldap002 slapd[22940]: conn=1001 op=4: attribute "entryCSN" index delete failure Oct 11 14:38:01 zre-ldap002 slapd[22940]: conn=1001 op=4 RESULT tag=103 err=80 text= Oct 11 14:38:01 zre-ldap002 slapd[22940]: slap_graduate_commit_csn: removing 0x41d4690 20121011213801.864697Z#000000#000#000000 Oct 11 14:38:01 zre-ldap002 slapd[22940]: conn=1001 fd=11 closed (connection lost) Oct 11 14:38:06 zre-ldap002 slapd[22940]: conn=1004 fd=14 closed (connection lost) Oct 11 14:38:09 zre-ldap002 slapd[22940]: conn=1005 fd=11 ACCEPT from IP=10.137.242.52:47811 (IP=10.137.242.52:389) Oct 11 14:38:09 zre-ldap002 slapd[22940]: conn=1005 op=0 EXT oid=1.3.6.1.4.1.1466.20037 Oct 11 14:38:09 zre-ldap002 slapd[22940]: conn=1005 op=0 STARTTLS Oct 11 14:38:09 zre-ldap002 slapd[22940]: conn=1005 op=0 RESULT oid= err=0 text= Oct 11 14:38:09 zre-ldap002 slapd[22940]: conn=1005 fd=11 TLS established tls_ssf=256 ssf=256 Oct 11 14:38:09 zre-ldap002 slapd[22940]: conn=1005 op=1 BIND dn="uid=zimbra,cn=admins,cn=zimbra" method=128 Oct 11 14:38:09 zre-ldap002 slapd[22940]: conn=1005 op=1 BIND dn="uid=zimbra,cn=admins,cn=zimbra" mech=SIMPLE ssf=0 Oct 11 14:38:09 zre-ldap002 slapd[22940]: conn=1005 op=1 RESULT tag=97 err=0 text= Oct 11 14:38:09 zre-ldap002 slapd[22940]: conn=1005 op=2 SRCH base="cn=zre-ldap002.eng.vmware.com,cn=servers,cn=zimbra" scope=0 deref=0 filter="(objectClass=*)" Oct 11 14:38:09 zre-ldap002 slapd[22940]: conn=1005 op=2 SEARCH RESULT tag=101 err=0 nentries=1 text= Oct 11 14:38:09 zre-ldap002 slapd[22940]: conn=1005 op=3 SRCH base="cn=config,cn=zimbra" scope=0 deref=0 filter="(objectClass=*)" Oct 11 14:38:09 zre-ldap002 slapd[22940]: conn=1005 op=3 SEARCH RESULT tag=101 err=0 nentries=1 text= Oct 11 14:38:10 zre-ldap002 slapd[22940]: conn=1005 op=4 MOD dn="cn=zre-ldap002.eng.vmware.com,cn=servers,cn=zimbra" Oct 11 14:38:10 zre-ldap002 slapd[22940]: conn=1005 op=4 MOD attr=zimbraMtaSmtpdMilters Oct 11 14:38:10 zre-ldap002 slapd[22940]: slap_queue_csn: queing 0x7f88c17fd1a0 20121011213810.017749Z#000000#000#000000 Oct 11 14:38:10 zre-ldap002 slapd[22940]: conn=1005 op=4: attribute "entryCSN" index delete failure Oct 11 14:38:10 zre-ldap002 slapd[22940]: conn=1005 op=4 RESULT tag=103 err=80 text= Oct 11 14:38:10 zre-ldap002 slapd[22940]: slap_graduate_commit_csn: removing 0x41d5110 20121011213810.017749Z#000000#000#000000 Oct 11 14:38:10 zre-ldap002 slapd[22940]: conn=1005 fd=11 closed (connection lost)

1 0

Re: (ITS#7415) Add MALLOC_CHECK_ and MALLOC_PERTURB_ libc env to the test suite for detecting heap corruption
by h.b.furuseth＠usit.uio.no 11 Oct '12

11 Oct '12

We can describe these and other variables in tests/README. Yeah I know, people don't read documentation. The testing announcements could mention the file though.

1 0

Re: (ITS#7415) Add MALLOC_CHECK_ and MALLOC_PERTURB_ libc env to the test suite for detecting heap corruption
by masarati＠aero.polimi.it 11 Oct '12

11 Oct '12

> It is true in general, but it is also a matter of a personal taste. If > the openldap project use a buildboot that set in the environment these > variables , that patch is useless. This is also partially true if the > openldap developer use to set these variables in their personal > environment, because other contributor could not do the same. Other > project use a similar patch , for example popt 1.17 devel and git 1.8 > in master, i am the author so i know . what is more openldap now are > not using automake and the little test environment that automake could > use, so i have some difficulty to understeand what is this alternative > "test environment" . Perhaps i have missed something ? I meant the environment of the shell tests are run from. IMHO, I'd consider setting those macros a developer's conscious choice rather than a normal user's act. Moreover, they're specific to glibc, while users might want to use different malloc implementations, or build on platforms where glibc is not available, so the fact they're not honored might not be obvious. My 2c, of course. p. -- Pierangelo Masarati Associate Professor Dipartimento di Ingegneria Aerospaziale Politecnico di Milano

1 0

Re: (ITS#7415) Add MALLOC_CHECK_ and MALLOC_PERTURB_ libc env to the test suite for detecting heap corruption
by Kurt＠OpenLDAP.org 11 Oct '12

11 Oct '12

And, I should add, setting them up generally (not just for OpenLDAP command line tools), means they catch non-OpenLDAP bugs... and that leads to non-OpenLDAP issues being reported to the OpenLDAP Project. We should avoid this for when 'make test' is simply used by deployers as a quick sanity tools. Developers, on the other hand, hopefully know what they are doing when they set such environmental variables... and they know how to manage this locally. Best to avoid adding such to the public test system. -- Kurt

1 0

Re: (ITS#7415) Add MALLOC_CHECK_ and MALLOC_PERTURB_ libc env to the test suite for detecting heap corruption
by Kurt＠OpenLDAP.org 11 Oct '12

11 Oct '12

I note that these environment variables are specific to Linux, and then only certain Linux systems. If we add these, then we should also add similar environment variables for FreeBSD malloc(3), MacOS/X malloc(3), and various alternative malloc(3) libraries. And then we might get into cases where variables for one set of environmental variables conflict with another. As these can be set by the developer as desired in their development environment, there's little reason to get into setting all the malloc(3) environmental variables that might be useful... and we shouldn't play favors and only set variables for Linux. -- Kurt

1 0

Re: (ITS#7415) Add MALLOC_CHECK_ and MALLOC_PERTURB_ libc env to the test suite for detecting heap corruption
by gitter.spiros＠gmail.com 11 Oct '12

11 Oct '12

It is true in general, but it is also a matter of a personal taste. If the openldap project use a buildboot that set in the environment these variables , that patch is useless. This is also partially true if the openldap developer use to set these variables in their personal environment, because other contributor could not do the same. Other project use a similar patch , for example popt 1.17 devel and git 1.8 in master, i am the author so i know . what is more openldap now are not using automake and the little test environment that automake could use, so i have some difficulty to understeand what is this alternative "test environment" . Perhaps i have missed something ? 2012/10/11, Pierangelo Masarati <masarati(a)aero.polimi.it>: > These vars can be set directly from the test environment, no need to > modify the test scripts. > > p. > >> Full_Name: Elia Pinto >> Version: 2.4 master >> OS: Linux FC12 >> URL: ftp://ftp.openldap.org/incoming/ >> Submission from: (NULL) (2605:4400:1:781:216:3eff:fe31:f4d4) >> >> >>>From a8ff21429c29f1d2b6ef8f58ec84b7a9036cea73 Mon Sep 17 00:00:00 2001 >> From: Elia Pinto <gitter.spiros(a)gmail.com> >> Date: Thu, 11 Oct 2012 17:49:06 +0200 >> Subject: [PATCH] Add MALLOC_CHECK_ and MALLOC_PERTURB_ libc env to the >> test >> suite for detecting heap corruption >> >> Recent versions of Linux libc (later than 5.4.23) and glibc (2.x) >> include a malloc() implementation which is tunable via environment >> variables. When MALLOC_CHECK_ is set, a special (less efficient) >> implementation is used which is designed to be tolerant against >> simple errors, such as double calls of free() with the same argument, >> or overruns of a single byte (off-by-one bugs). When MALLOC_CHECK_ >> is set to 3, a diagnostic message is printed on stderr >> and the program is aborted. >> >> Setting the MALLOC_PERTURB_ environment variable causes the malloc >> functions in libc to return memory which has been wiped and clear >> memory when it is returned. >> Of course this does not affect calloc which always does clear the memory. >> >> The reason for this exercise is, of course, to find code which uses >> memory returned by malloc without initializing it and code which uses >> code after it is freed. valgrind can do this but it's costly to run. >> The MALLOC_PERTURB_ exchanges the ability to detect problems in 100% >> of the cases with speed. >> >> The byte value used to initialize values returned by malloc is the byte >> value of the environment value. The value used to clear memory is the >> bitwise inverse. Setting MALLOC_PERTURB_ to zero disables the feature. >> >> This technique can find hard to detect bugs. >> It is therefore suggested to always use this flag (at least temporarily) >> when testing out code or a new distribution. >> >> Signed-off-by: Elia Pinto <gitter.spiros(a)gmail.com> >> --- >> tests/run.in | 5 +++++ >> 1 file changed, 5 insertions(+) >> >> diff --git a/tests/run.in b/tests/run.in >> index 5e6178b..fe25d0c 100644 >> --- a/tests/run.in >> +++ b/tests/run.in >> @@ -241,6 +241,11 @@ fi >> >> # disable LDAP initialization >> LDAPNOINIT=true; export LDAPNOINIT >> +# Add libc malloc_check and MALLOC_PERTURB test >> +MALLOC_CHECK_=3 >> +export MALLOC_CHECK_ >> +MALLOC_PERTURB_="$( expr $ $$ % 255 $ + 1)" >> +export MALLOC_PERTURB_ >> >> echo "Running ${SCRIPT} for ${BACKEND}..." >> while [ $COUNTER -le $LOOP ]; do >> -- >> 1.7.11.rc1 >> >> >> >> >> >> > > > -- > Pierangelo Masarati > Associate Professor > Dipartimento di Ingegneria Aerospaziale > Politecnico di Milano > > -- Inviato dal mio dispositivo mobile

1 0

Re: (ITS#7415) Add MALLOC_CHECK_ and MALLOC_PERTURB_ libc env to the test suite for detecting heap corruption
by masarati＠aero.polimi.it 11 Oct '12

11 Oct '12

These vars can be set directly from the test environment, no need to modify the test scripts. p. > Full_Name: Elia Pinto > Version: 2.4 master > OS: Linux FC12 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (2605:4400:1:781:216:3eff:fe31:f4d4) > > >>From a8ff21429c29f1d2b6ef8f58ec84b7a9036cea73 Mon Sep 17 00:00:00 2001 > From: Elia Pinto <gitter.spiros(a)gmail.com> > Date: Thu, 11 Oct 2012 17:49:06 +0200 > Subject: [PATCH] Add MALLOC_CHECK_ and MALLOC_PERTURB_ libc env to the > test > suite for detecting heap corruption > > Recent versions of Linux libc (later than 5.4.23) and glibc (2.x) > include a malloc() implementation which is tunable via environment > variables. When MALLOC_CHECK_ is set, a special (less efficient) > implementation is used which is designed to be tolerant against > simple errors, such as double calls of free() with the same argument, > or overruns of a single byte (off-by-one bugs). When MALLOC_CHECK_ > is set to 3, a diagnostic message is printed on stderr > and the program is aborted. > > Setting the MALLOC_PERTURB_ environment variable causes the malloc > functions in libc to return memory which has been wiped and clear > memory when it is returned. > Of course this does not affect calloc which always does clear the memory. > > The reason for this exercise is, of course, to find code which uses > memory returned by malloc without initializing it and code which uses > code after it is freed. valgrind can do this but it's costly to run. > The MALLOC_PERTURB_ exchanges the ability to detect problems in 100% > of the cases with speed. > > The byte value used to initialize values returned by malloc is the byte > value of the environment value. The value used to clear memory is the > bitwise inverse. Setting MALLOC_PERTURB_ to zero disables the feature. > > This technique can find hard to detect bugs. > It is therefore suggested to always use this flag (at least temporarily) > when testing out code or a new distribution. > > Signed-off-by: Elia Pinto <gitter.spiros(a)gmail.com> > --- > tests/run.in | 5 +++++ > 1 file changed, 5 insertions(+) > > diff --git a/tests/run.in b/tests/run.in > index 5e6178b..fe25d0c 100644 > --- a/tests/run.in > +++ b/tests/run.in > @@ -241,6 +241,11 @@ fi > > # disable LDAP initialization > LDAPNOINIT=true; export LDAPNOINIT > +# Add libc malloc_check and MALLOC_PERTURB test > +MALLOC_CHECK_=3 > +export MALLOC_CHECK_ > +MALLOC_PERTURB_="$( expr $ $$ % 255 $ + 1)" > +export MALLOC_PERTURB_ > > echo "Running ${SCRIPT} for ${BACKEND}..." > while [ $COUNTER -le $LOOP ]; do > -- > 1.7.11.rc1 > > > > > > -- Pierangelo Masarati Associate Professor Dipartimento di Ingegneria Aerospaziale Politecnico di Milano

1 0

Re: (ITS#7415) Add MALLOC_CHECK_ and MALLOC_PERTURB_ libc env to the test suite for detecting heap corruption
by gitter.spiros＠gmail.com 11 Oct '12

11 Oct '12

You can also pull from git://github.com/devzero2000/openldap.git 2012/10/11 <openldap-its(a)openldap.org>: > > *** THIS IS AN AUTOMATICALLY GENERATED REPLY *** > > Thanks for your report to the OpenLDAP Issue Tracking System. Your > report has been assigned the tracking number ITS#7415. > > One of our support engineers will look at your report in due course. > Note that this may take some time because our support engineers > are volunteers. They only work on OpenLDAP when they have spare > time. > > If you need to provide additional information in regards to your > issue report, you may do so by replying to this message. Note that > any mail sent to openldap-its(a)openldap.org with (ITS#7415) > in the subject will automatically be attached to the issue report. > > mailto:openldap-its@openldap.org?subject=(ITS#7415) > > You may follow the progress of this report by loading the following > URL in a web browser: > http://www.OpenLDAP.org/its/index.cgi?findid=7415 > > Please remember to retain your issue tracking number (ITS#7415) > on any further messages you send to us regarding this report. If > you don't then you'll just waste our time and yours because we > won't be able to properly track the report. > > Please note that the Issue Tracking System is not intended to > be used to seek help in the proper use of OpenLDAP Software. > Such requests will be closed. > > OpenLDAP Software is user supported. > http://www.OpenLDAP.org/support/ > > -------------- > Copyright 1998-2007 The OpenLDAP Foundation, All Rights Reserved. >

1 0

(ITS#7415) Add MALLOC_CHECK_ and MALLOC_PERTURB_ libc env to the test suite for detecting heap corruption
by gitter.spiros＠gmail.com 11 Oct '12

11 Oct '12

Full_Name: Elia Pinto Version: 2.4 master OS: Linux FC12 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (2605:4400:1:781:216:3eff:fe31:f4d4) >From a8ff21429c29f1d2b6ef8f58ec84b7a9036cea73 Mon Sep 17 00:00:00 2001 From: Elia Pinto <gitter.spiros(a)gmail.com> Date: Thu, 11 Oct 2012 17:49:06 +0200 Subject: [PATCH] Add MALLOC_CHECK_ and MALLOC_PERTURB_ libc env to the test suite for detecting heap corruption Recent versions of Linux libc (later than 5.4.23) and glibc (2.x) include a malloc() implementation which is tunable via environment variables. When MALLOC_CHECK_ is set, a special (less efficient) implementation is used which is designed to be tolerant against simple errors, such as double calls of free() with the same argument, or overruns of a single byte (off-by-one bugs). When MALLOC_CHECK_ is set to 3, a diagnostic message is printed on stderr and the program is aborted. Setting the MALLOC_PERTURB_ environment variable causes the malloc functions in libc to return memory which has been wiped and clear memory when it is returned. Of course this does not affect calloc which always does clear the memory. The reason for this exercise is, of course, to find code which uses memory returned by malloc without initializing it and code which uses code after it is freed. valgrind can do this but it's costly to run. The MALLOC_PERTURB_ exchanges the ability to detect problems in 100% of the cases with speed. The byte value used to initialize values returned by malloc is the byte value of the environment value. The value used to clear memory is the bitwise inverse. Setting MALLOC_PERTURB_ to zero disables the feature. This technique can find hard to detect bugs. It is therefore suggested to always use this flag (at least temporarily) when testing out code or a new distribution. Signed-off-by: Elia Pinto <gitter.spiros(a)gmail.com> --- tests/run.in | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/tests/run.in b/tests/run.in index 5e6178b..fe25d0c 100644 --- a/tests/run.in +++ b/tests/run.in @@ -241,6 +241,11 @@ fi # disable LDAP initialization LDAPNOINIT=true; export LDAPNOINIT +# Add libc malloc_check and MALLOC_PERTURB test +MALLOC_CHECK_=3 +export MALLOC_CHECK_ +MALLOC_PERTURB_="$( expr $ $$ % 255 $ + 1)" +export MALLOC_PERTURB_ echo "Running ${SCRIPT} for ${BACKEND}..." while [ $COUNTER -le $LOOP ]; do -- 1.7.11.rc1

1 0

Re: (ITS#7414) rwm: ldapmodify, slapd segmentation fault
by hyc＠symas.com 11 Oct '12

11 Oct '12

jvcelak(a)redhat.com wrote: > Full_Name: Jan Vcelak > Version: 2.4.33 > OS: Linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (209.132.186.34) > > > Hello, > > it is possible to crash slapd in certain configuration with rwm overlay enabled, > using specific ldapmodify. This problem seems to be present for a very long > time. > > Configuration used (slapd.ldif): > > dn: cn=config > objectClass: olcGlobal > cn: config > olcArgsFile: /var/run/openldap/slapd.args > olcPidFile: /var/run/openldap/slapd.pid > > dn: cn=module,cn=config > objectClass: olcModuleList > cn: module > olcModulepath: /usr/lib64/openldap > olcModuleload: rwm.la > > dn: cn=schema,cn=config > objectClass: olcSchemaConfig > cn: schema > > include: file:///etc/openldap/schema/core.ldif > include: file:///etc/openldap/schema/cosine.ldif > include: file:///etc/openldap/schema/inetorgperson.ldif > > dn: olcDatabase=frontend,cn=config > objectClass: olcDatabaseConfig > olcDatabase: frontend > > dn: olcDatabase=hdb,cn=config > objectClass: olcDatabaseConfig > objectClass: olcHdbConfig > olcDatabase: hdb > olcSuffix: dc=my-domain,dc=com > olcRootDN: cn=Manager,dc=my-domain,dc=com > olcRootPW: secret > olcDbDirectory: /var/lib/ldap > olcDbIndex: objectClass eq,pres > olcDbIndex: ou,cn,mail,surname,givenname eq,pres,sub > > dn: olcOverlay=rwm,olcDatabase={1}hdb,cn=config > objectClass: olcOverlayConfig > objectClass: olcRwmConfig > olcOverlay: rwm > olcRwmRewrite: {0}rwm-rewriteEngine "on" > olcRwmRewrite: {1}rwm-rewriteContext "bindDN" > olcRwmRewrite: {2}rwm-rewriteRule "cn=([a-z]+),ou=People,dc=my-domain,dc=com" > "uid=$1,ou=People,dc=my-domain,dc=com" > > > Set up and start the server. Add the initial data: > > dn: dc=my-domain,dc=com > objectClass: dcObject > objectClass: organizationalUnit > description: Root LDAP entry > dc: my-domain > ou: rootobject > > dn: cn=Manager,dc=my-domain,dc=com > objectClass: organizationalRole > cn: Manager > > dn: ou=People,dc=my-domain,dc=com > objectClass: top > objectClass: organizationalunit > ou: People > > dn: cn=test1,ou=People,dc=my-domain,dc=com > objectClass: inetOrgPerson > cn: test1 > sn: test > > > Perform following modify operation: > > dn: cn=test1,ou=People,dc=my-domain,dc=com > changetype: modrdn > newrdn: cn=test2 > deleteoldrdn: 1 > newsuperior: ou=People,dc=my-domain,dc=com > > > The slapd daemon will crash, here is the full backtrace: Thanks for the detailed report. Fixed now in master. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#7413) Some UTF-8 characters are wrongly recognized as identical in multi-valued attributes
by michail.bachmann＠cms.hu-berlin.de 11 Oct '12

11 Oct '12

--nextPart1483759.4qzvGhZdbd Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable On Thursday 11 October 2012, Howard Chu wrote: > m.bachmann(a)cms.hu-berlin.de wrote: > > Full_Name: Michail Bachmann > > Version: 2.4.31 > > OS: Linux > > URL: ftp://ftp.openldap.org/incoming/ > > Submission from: (NULL) (141.20.3.158) > > > > > > > > The UTF-8 character 'FEMININE ORDINAL INDICATOR' (U+00AA) is wrongly tr= eated as > > 'LATIN SMALL LETTER A' (U+0061), so adding a multi-valued attribute whe= re U+00AA > > is replaced with U+0061 (or the other way around) fails: >=20 > This works as designed. See the Unicode specification, rules for decompos= ition. Ah, ok. Thank you for your time and sorry for the noise. > > > > $ ldapadd -f create.ldif -h localhost -D 'cn=3Dadmin,dc=3Dexample,dc=3D= com' > > > > ### create.ldif ### > > dn: cn=3Dtest,dc=3Dexample,dc=3Dcom > > objectClass: organizationalRole > > objectClass: top > > cn: test > > street: a street > > ### /create.ldif ### > > > > $ ldapmodify -f modify.ldif -h localhost -D 'cn=3Dadmin,dc=3Dexample,dc= =3Dcom' > > > > ### modify.ldif ### > > dn: cn=3Dtest,dc=3Dexample,dc=3Dcom > > changetype: modify > > add: street > > street: =C2=AA street > > - > > > > ### /modify.ldif ### > > > > will result in > > > > ldap_modify: Type or value exists (20) > > additional info: modify/add: street: value #0 already exists > > > > It seems like U+00AA is decomposed into '<super>+U+0061' and then the '= <super>' > > part is discarded. > > > > Tested with 2.4.31 (Debian) and 2.4.21 (Ubuntu) > > > > > > >=20 >=20 >=20 --nextPart1483759.4qzvGhZdbd Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Disposition: attachment; filename="smime.p7s" Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIOYTCCBCEw ggMJoAMCAQICAgDHMA0GCSqGSIb3DQEBBQUAMHExCzAJBgNVBAYTAkRFMRwwGgYDVQQKExNEZXV0 c2NoZSBUZWxla29tIEFHMR8wHQYDVQQLExZULVRlbGVTZWMgVHJ1c3QgQ2VudGVyMSMwIQYDVQQD ExpEZXV0c2NoZSBUZWxla29tIFJvb3QgQ0EgMjAeFw0wNjEyMTkxMDI5MDBaFw0xOTA2MzAyMzU5 MDBaMFoxCzAJBgNVBAYTAkRFMRMwEQYDVQQKEwpERk4tVmVyZWluMRAwDgYDVQQLEwdERk4tUEtJ MSQwIgYDVQQDExtERk4tVmVyZWluIFBDQSBHbG9iYWwgLSBHMDEwggEiMA0GCSqGSIb3DQEBAQUA A4IBDwAwggEKAoIBAQDpm8NnhfkNrvWNVMOWUDU9YuluTO2U1wBblSJ01CDrNI/W7MAxBAuZgeKm FNJSoCgjhIt0iQReW+DieMF4yxbLKDU5ey2QRdDtoAB6fL9KDhsAw4bpXCsxEXsM84IkQ4wcOItq aACa7txPeKvSxhObdq3u3ibo7wGvdA/BCaL2a869080UME/15eOkyGKbghoDJzANAmVgTe3RCSMq ljVYJ9N2xnG2kB3E7f81hn1vM7PbD8URwoqDoZRdQWvY0hD1TP3KUazZve+Sg7va64sWVlZDz+HV Ez2mHycwzUlU28kTNJpxdcVs6qcLmPkhnSevPqM5OUhqjK3JmfvDEvK9AgMBAAGjgdkwgdYwcAYD VR0fBGkwZzBloGOgYYZfaHR0cDovL3BraS50ZWxlc2VjLmRlL2NnaS1iaW4vc2VydmljZS9hZl9E b3dubG9hZEFSTC5jcmw/LWNybF9mb3JtYXQ9WF81MDkmLWlzc3Vlcj1EVF9ST09UX0NBXzIwHQYD VR0OBBYEFEm3xs/oPR9/6kR7Eyn38QpwPt5kMB8GA1UdIwQYMBaAFDHDeRu69VPXF+CJei0XbAqz K50zMA4GA1UdDwEB/wQEAwIBBjASBgNVHRMBAf8ECDAGAQH/AgECMA0GCSqGSIb3DQEBBQUAA4IB AQA74Vp3wEgX3KkY7IGvWonwvSiSpspZGBJw7Cjy565/lizn8l0ZMfYTK3S9vYCyufdnyTmieTvh ERHua3iRM347XyYndVNljjNj7s9zw7CSI0khUHUjoR8Y4pSFPT8z6XcgjaK95qGFKUD2P3MyWA0J a6bahWzAP7uNZmRWJE6uDT8yNQFb6YyC2XJZT7GGhfF0hVblw/hc843uR7NTBXDn5U2KaYMo4RMJ hp5eyOpYHgwf+aTUWgRo/Sg+iwK2WLX2oSw3VwBnqyNojWOl75lrXP1LVvarQIc01BGSbOyHxQoL BzNytG8MHVQs2FHHzL8w00Ny8TK/jM5JY6gA9/IcMIIE9DCCA9ygAwIBAgIEC2I0jzANBgkqhkiG 9w0BAQUFADBaMQswCQYDVQQGEwJERTETMBEGA1UEChMKREZOLVZlcmVpbjEQMA4GA1UECxMHREZO LVBLSTEkMCIGA1UEAxMbREZOLVZlcmVpbiBQQ0EgR2xvYmFsIC0gRzAxMB4XDTA3MTEyMDEwMjky MVoXDTE5MDYzMDAwMDAwMFowaDELMAkGA1UEBhMCREUxKDAmBgNVBAoTH0h1bWJvbGR0LVVuaXZl cnNpdGFldCB6dSBCZXJsaW4xDjAMBgNVBAMTBUhVLUNBMR8wHQYJKoZIhvcNAQkBFhBwa2lAaHUt YmVybGluLmRlMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA6wxB17AojABvR7rEkR8v 3wfquJ1RAGBx9Bhv0pQis98kCJaaYYO1cspc0znfEAOcBk9lBhb/sWfV13KFKDcib7WlY1sFBHCJ AbGkpcNTfqp/enTtDZOzXFUzXOj5+lcaHwn6qt2HQ7oafm8wfPp9efd3ykRzCWhbZ7K3o/kCCMHw 5Dxe9na4OdQCXqwp6Hhpmx9CGHq2SPWxrRZqdZJzmfhmDV3yVYghIuyHN/jDTorshki3pWF3OFHp ok1w09LKPDUZRdHZzUt7ZIZYEwdvjVAKJAsHyKjzrASRfHJgXvJQLENcBJwPGXfJGMSXj3AcS9Cj wQdtMlyDsU4D5RV4BQIDAQABo4IBsjCCAa4wEgYDVR0TAQH/BAgwBgEB/wIBATALBgNVHQ8EBAMC AQYwHQYDVR0OBBYEFB/1LD73QKsukKBq0+J5XvJ2zYN0MB8GA1UdIwQYMBaAFEm3xs/oPR9/6kR7 Eyn38QpwPt5kMBsGA1UdEQQUMBKBEHBraUBodS1iZXJsaW4uZGUwgYgGA1UdHwSBgDB+MD2gO6A5 hjdodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2dsb2JhbC1yb290LWNhL3B1Yi9jcmwvY2FjcmwuY3Js MD2gO6A5hjdodHRwOi8vY2RwMi5wY2EuZGZuLmRlL2dsb2JhbC1yb290LWNhL3B1Yi9jcmwvY2Fj cmwuY3JsMIGiBggrBgEFBQcBAQSBlTCBkjBHBggrBgEFBQcwAoY7aHR0cDovL2NkcDEucGNhLmRm bi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwRwYIKwYBBQUHMAKGO2h0 dHA6Ly9jZHAyLnBjYS5kZm4uZGUvZ2xvYmFsLXJvb3QtY2EvcHViL2NhY2VydC9jYWNlcnQuY3J0 MA0GCSqGSIb3DQEBBQUAA4IBAQBO3AOzYN+zVEPJLJHP12+Oa7wzhC2aji1SGLkPHqYnl27d2+Fx XgOo24p+rC7vS53tLGjE41EfkwEgO+cy4J9mUptTlDqa3gvzkR8C95Yl43fmYd5HJrZ+WqQTVddw hxnOBCY0f+oW+RmeybR6TYDAQ+ByK6ru6DFPBRQpIejuny75jjm0EZzcPwZZJ+gxObQ67RtMxiFk 6Io6jWRdpy40mDJ39NF1tJqAFxo+3hSKVRTVs1l/ML12lLmTq+tgri9bLBEQLwNoaCjGhn2aOMYJ B0Rd5a31pbiXEZLV4IBylWd5/y3Nfb9q3x+i1lXI05u+oJ3q9ox4PbuuKU3VWIngMIIFQDCCBCig AwIBAgIHE9HfrnKfDDANBgkqhkiG9w0BAQUFADBoMQswCQYDVQQGEwJERTEoMCYGA1UEChMfSHVt Ym9sZHQtVW5pdmVyc2l0YWV0IHp1IEJlcmxpbjEOMAwGA1UEAxMFSFUtQ0ExHzAdBgkqhkiG9w0B CQEWEHBraUBodS1iZXJsaW4uZGUwHhcNMTIwNTE1MTQwMzEwWhcNMTUwNTE1MTQwMzEwWjBnMQsw CQYDVQQGEwJERTEoMCYGA1UEChMfSHVtYm9sZHQtVW5pdmVyc2l0YWV0IHp1IEJlcmxpbjETMBEG A1UECxMKQ01TL0FidC4gMTEZMBcGA1UEAxMQTWljaGFpbCBCYWNobWFubjCCASIwDQYJKoZIhvcN AQEBBQADggEPADCCAQoCggEBANiS1EZ9eoDkVZnlHdoqGKJD6WNnV16udnQKT7j5yHTRo5XnF7LB 3nagMKWopr84yVnqRnRay3O2IhmHsscAisJ4uENXeVed5g9QVBGAKUmUAy3jgcKXJ84PJNYXMy93 YN3tzi2VKwwbpM4pBDfC4FT2V4jsb1jynwH5ayoKpbt8d7oggwL3xr/l90h8gJoNW5LFcIgBKDll tWaHSHqytquHn859eNNxTDntFbgTgh9RGLaI6Kp+P9XBqrqLFX1ebWe24/MSHw6B2Pw2ny/Vy54A e3W/7FSxpLDCKllQiSbgqG5eyUWEsTOAG41D4Z56AHKcx8byks8j+A6E1xpCWfMCAwEAAaOCAe4w ggHqMBwGA1UdIAQVMBMwEQYPKwYBBAGBrSGCLAEBBAICMAkGA1UdEwQCMAAwCwYDVR0PBAQDAgXg MB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAdBgNVHQ4EFgQUALsSnuznKfPHjGGxfAJr jZmz544wHwYDVR0jBBgwFoAUH/UsPvdAqy6QoGrT4nle8nbNg3QwLAYDVR0RBCUwI4EhbWljaGFp bC5iYWNobWFubkBjbXMuaHUtYmVybGluLmRlMIGDBgNVHR8EfDB6MDugOaA3hjVodHRwOi8vY2Rw MS5wY2EuZGZuLmRlL2h1LWJlcmxpbi1jYS9wdWIvY3JsL2NhY3JsLmNybDA7oDmgN4Y1aHR0cDov L2NkcDIucGNhLmRmbi5kZS9odS1iZXJsaW4tY2EvcHViL2NybC9jYWNybC5jcmwwgZ4GCCsGAQUF BwEBBIGRMIGOMEUGCCsGAQUFBzAChjlodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2h1LWJlcmxpbi1j YS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwRQYIKwYBBQUHMAKGOWh0dHA6Ly9jZHAyLnBjYS5kZm4u ZGUvaHUtYmVybGluLWNhL3B1Yi9jYWNlcnQvY2FjZXJ0LmNydDANBgkqhkiG9w0BAQUFAAOCAQEA GrSDIsaKf9b6gt658mbHwV4bMO+YvsqpX8x/vQxRnAp7DvpLiHbAawWlDcOPKqkccmk6egUUeoMQ GICvA3FjCAJlWdNc3/A9ec1yWD2XEH56/uXWkf3Nny7SqnvMJRxPkwjidc/WP5xmuvsQScDm7Je2 jasRmvS5TFBVjNb/yEI56xBGCr1J+s3WeR8ILHsMXvP8ll9rRXI3GQHqx7jhw0FOFjuXKNdzBgLI 1DMcrAqQZeA8tyQxO0zCe53hHTCoJp3fYxYD5EDT8pM7X0woSdOKUmKl4ezUBNizYW55vx10IbFF j2VTQnTs3fCgRMyMH4dAm0DBeejarZDbKobPxTGCAiQwggIgAgEBMHMwaDELMAkGA1UEBhMCREUx KDAmBgNVBAoTH0h1bWJvbGR0LVVuaXZlcnNpdGFldCB6dSBCZXJsaW4xDjAMBgNVBAMTBUhVLUNB MR8wHQYJKoZIhvcNAQkBFhBwa2lAaHUtYmVybGluLmRlAgcT0d+ucp8MMAkGBSsOAwIaBQCggYcw GAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTIxMDExMTQyMzQzWjAj BgkqhkiG9w0BCQQxFgQUvEheLrh+IXZtXeaWZ0lHReCaO/MwKAYJKoZIhvcNAQkPMRswGTALBglg hkgBZQMEAQIwCgYIKoZIhvcNAwcwDQYJKoZIhvcNAQEBBQAEggEAGUem6qtixM8FdGDrjHhOypJh sbIYybMQMw5UKtWqVkne4VuLIVru8PWqh88D1uW/zpB3I0gZwhlDfiM/2tykwvNUDRAU1BAi19M3 XI8xVt0zi62uAbpD7QeEdbFwGry/7Tz5kgYp1DCjSfSni9FNT2NZVRPe749HhR89SHmUi1SwjDli LTGTur8KWnnWvJIIK7g5GCzPNpV1zeB6PiBTY5nr9w05Ro/mUgrrPlz4StsOY9eiPhRuEeAbXrnb 4zVnksaDExLf4QyKD3ikK4tadvfVO5Lph4XJySeHE/MiMRRI4gAekLvWZgdLMqeo6xM2nf52+vX6 UefhhpBc5gvH/QAAAAAAAA== --nextPart1483759.4qzvGhZdbd--

1 0

(ITS#7414) rwm: ldapmodify, slapd segmentation fault
by jvcelak＠redhat.com 11 Oct '12

11 Oct '12

Full_Name: Jan Vcelak Version: 2.4.33 OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (209.132.186.34) Hello, it is possible to crash slapd in certain configuration with rwm overlay enabled, using specific ldapmodify. This problem seems to be present for a very long time. Configuration used (slapd.ldif): dn: cn=config objectClass: olcGlobal cn: config olcArgsFile: /var/run/openldap/slapd.args olcPidFile: /var/run/openldap/slapd.pid dn: cn=module,cn=config objectClass: olcModuleList cn: module olcModulepath: /usr/lib64/openldap olcModuleload: rwm.la dn: cn=schema,cn=config objectClass: olcSchemaConfig cn: schema include: file:///etc/openldap/schema/core.ldif include: file:///etc/openldap/schema/cosine.ldif include: file:///etc/openldap/schema/inetorgperson.ldif dn: olcDatabase=frontend,cn=config objectClass: olcDatabaseConfig olcDatabase: frontend dn: olcDatabase=hdb,cn=config objectClass: olcDatabaseConfig objectClass: olcHdbConfig olcDatabase: hdb olcSuffix: dc=my-domain,dc=com olcRootDN: cn=Manager,dc=my-domain,dc=com olcRootPW: secret olcDbDirectory: /var/lib/ldap olcDbIndex: objectClass eq,pres olcDbIndex: ou,cn,mail,surname,givenname eq,pres,sub dn: olcOverlay=rwm,olcDatabase={1}hdb,cn=config objectClass: olcOverlayConfig objectClass: olcRwmConfig olcOverlay: rwm olcRwmRewrite: {0}rwm-rewriteEngine "on" olcRwmRewrite: {1}rwm-rewriteContext "bindDN" olcRwmRewrite: {2}rwm-rewriteRule "cn=([a-z]+),ou=People,dc=my-domain,dc=com" "uid=$1,ou=People,dc=my-domain,dc=com" Set up and start the server. Add the initial data: dn: dc=my-domain,dc=com objectClass: dcObject objectClass: organizationalUnit description: Root LDAP entry dc: my-domain ou: rootobject dn: cn=Manager,dc=my-domain,dc=com objectClass: organizationalRole cn: Manager dn: ou=People,dc=my-domain,dc=com objectClass: top objectClass: organizationalunit ou: People dn: cn=test1,ou=People,dc=my-domain,dc=com objectClass: inetOrgPerson cn: test1 sn: test Perform following modify operation: dn: cn=test1,ou=People,dc=my-domain,dc=com changetype: modrdn newrdn: cn=test2 deleteoldrdn: 1 newsuperior: ou=People,dc=my-domain,dc=com The slapd daemon will crash, here is the full backtrace: #0 rwm_op_rollback (op=op@entry=0x7fffe8000930, ros=0x7fffe8001738, rs=<optimized out>) at rwm.c:110 No locals. #1 0x00007ffff210f1c2 in rwm_op_cleanup (op=0x7fffe8000930, rs=<optimized out>) at rwm.c:165 cb = 0x7fffe8001718 ros = <optimized out> #2 0x00005555555a606b in slap_cleanup_play (op=op@entry=0x7fffe8000930, rs=rs@entry=0x7ffff1106930) at result.c:541 sc_next = 0x7ffff11065c0 sc_nextp = 0x7fffe8001718 sc = 0x7fffe8001718 scp = 0x7ffff1106018 #3 0x00005555555a6573 in send_ldap_response (op=op@entry=0x7fffe8000930, rs=rs@entry=0x7ffff1106930) at result.c:733 berbuf = { buffer = "\000\000\001\000\001\000\000\000\377\377\377\377\377\377\377\377", '\000' <repeats 24 times>, "F\030\000\350\377\177\000\000\024(\000\350\377\177\000\000\000\000\000\000\000\000\000\000F\030\000\350\377\177\000\000\320\016\000\350\377\177\000\000P\373\275UUU\000\000\200v\357\367\377\177\000\000\001\000\000\000hw\001", '\000' <repeats 17 times>"\266, \252r\367\377\177", '\000' <repeats 11 times>, "a\370<\316m]\037\200*\227\367\377\177\000\000\001\000\000\000UU\000\000\321\323vP\000\000\000\000\350\n\000\350\377\177\000\000\003", '\000' <repeats 23 times>"\225, \362\227\367\311\362\245\303\000\000\000\000\000\000\000\000+\246fUUU\000\000\030ӿUUU\000\000\223\204+\366\377\177\000\000\060\065\020\350\377\177\000\000\000a\370<\316m]\037", ialign = 65536, lalign = 4295032832, falign = 9.18354962e-41, dalign = 2.1220281700514382e-314, palign = 0x100010000 <Address 0x100010000 out of bounds>} ber = <optimized out> rc = 32768 bytes = <optimized out> __PRETTY_FUNCTION__ = "send_ldap_response" #4 0x00005555555a7126 in slap_send_ldap_result (op=0x7fffe8000930, rs=0x7ffff1106930) at result.c:860 tmp = 0x0 otext = 0x0 oref = 0x0 __PRETTY_FUNCTION__ = "slap_send_ldap_result" #5 0x0000555555621a50 in hdb_modrdn (op=0x7fffe8000930, rs=0x7ffff1106930) at modrdn.c:789 bdb = 0x5555559fa4f0 children = 0x55555599d260 entry = 0x55555599cfc0 p_dn = {bv_len = 29, bv_val = 0x7fffe8102399 "ou=People,dc=my-domain,dc=com"} p_ndn = {bv_len = 29, bv_val = 0x7fffe81023c9 ""} new_dn = {bv_len = 38, bv_val = 0x0} new_ndn = {bv_len = 38, bv_val = 0x0} e = <optimized out> p = <optimized out> ei = 0x7fffe8103f00 eip = 0x7fffe410a0a0 nei = 0x7fffe410a0a0 neip = 0x0 textbuf = "0\t\000\350\377\177\000\000\000e\020\361\377\177\000\000 i\237UUU\000\000\230\060\021\362\377\177\000\000\200\241^\366\377\177\000\000\000\000\000\000\316m]\037&\000\000\000\000\000\000\000\060\022\000\350\377\177\000\000\060\t\000\350\377\177\000\000\070\027\000\350\377\177\000\000\000\000\000\000\000\000\000\000)\323\020\362\377\177\000\000&\000\000\000\000\000\000\000\060\022\000\350\377\177\000\000&\000\000\000\000\000\000\000\270\022\000\350\377\177\000\000\000k\237UUU\000\000\000\352\242UUU\000\000\314X\021\362\377\177\000\000\060i\020\361\377\177\000\000\030\027\000\350\377\177\000\000\030\027\000\350\377\177\000\000\060i\020\361\377\177\000\000\332\326\020\362\377\177\000\000\360d\020\361\377\177\000\000\020e\020\361\377\177\000\000\b\000\000\000\000\000\000\000\270\023\000\350\377\177\000\000\b\000\000\000\000\000\000\000\350\023\000\350\377\177\000\000\000k\237UUU\000\000\000\352\242UUU\000" ltid = 0x0 lt2 = 0x7fffe81068f0 opinfo = {boi_oe = {oe_next = {sle_next = 0x0}, oe_key = 0x0}, boi_txn = 0x7fffe8106730, boi_locks = 0x0, boi_err = 0, boi_acl_cache = 0 '\000', boi_flag = 0 '\000'} dummy = {e_id = 4, e_name = {bv_len = 38, bv_val = 0x7fffe8106890 "cn=test2,ou=People,dc=my-domain,dc=com"}, e_nname = { bv_len = 38, bv_val = 0x7fffe81068c0 "cn=test2,ou=people,dc=my-domain,dc=com"}, e_attrs = 0x0, e_ocflags = 256, e_bv = { bv_len = 0, bv_val = 0x0}, e_private = 0x7fffe8103f00} np = <optimized out> np_dn = <optimized out> np_ndn = <optimized out> new_parent_dn = <optimized out> manageDSAit = 0 lock = {off = 164424, ndx = 98, gen = 2, mode = DB_LOCK_WRITE} plock = {off = 157848, ndx = 932, gen = 2, mode = DB_LOCK_READ} nplock = {off = 0, ndx = 1436511616, gen = 21845, mode = 4044383224} num_retries = 0 preread_ctrl = 0x0 postread_ctrl = 0x0 ctrls = {0x0, 0x555555a2ea00, 0x0, 0x7ffff11064a0, 0x7ffff1106480, 0x7ffff1106450} num_ctrls = 0 rc = <optimized out> parent_is_glue = 0 parent_is_leaf = 1 __PRETTY_FUNCTION__ = "hdb_modrdn" #6 0x0000555555603c96 in overlay_op_walk (op=op@entry=0x7fffe8000930, rs=0x7ffff1106930, which=op_modrdn, oi=0x5555559f76b0, on=0x0) at backover.c:671 func = <optimized out> rc = 32768 #7 0x0000555555603deb in over_op_func (op=0x7fffe8000930, rs=<optimized out>, which=<optimized out>) at backover.c:723 oi = <optimized out> on = <optimized out> be = 0x5555559fa350 db = {bd_info = 0x5555558e3620, bd_self = 0x5555559fa350, be_ctrls = "\000\001\001\001\000\001\000\000\001\000\000\001\001\000\001", '\000' <repeats 17 times>, "\001", be_flags = 2312, be_restrictops = 0, be_requires = 0, be_ssf_set = {sss_ssf = 0, sss_transport = 0, sss_tls = 0, sss_sasl = 0, sss_update_ssf = 0, sss_update_transport = 0, sss_update_tls = 0, sss_update_sasl = 0, sss_simple_bind = 0}, be_suffix = 0x555555a1df40, be_nsuffix = 0x555555a1df70, be_schemadn = {bv_len = 0, bv_val = 0x0}, be_schemandn = { bv_len = 0, bv_val = 0x0}, be_rootdn = {bv_len = 30, bv_val = 0x555555a1e010 "cn=Manager,dc=my-domain,dc=com"}, be_rootndn = {bv_len = 30, bv_val = 0x555555a1e060 "cn=manager,dc=my-domain,dc=com"}, be_rootpw = {bv_len = 6, bv_val = 0x555555a1dee0 "secret"}, be_max_deref_depth = 15, be_def_limit = {lms_t_soft = 3600, lms_t_hard = 0, lms_s_soft = 500, lms_s_hard = 0, lms_s_unchecked = -1, lms_s_pr = 0, lms_s_pr_hide = 0, lms_s_pr_total = 0}, be_limits = 0x0, be_acl = 0x0, be_dfltaccess = ACL_READ, be_extra_anlist = 0x0, be_update_ndn = {bv_len = 0, bv_val = 0x0}, be_update_refs = 0x0, be_pending_csn_list = 0x555555bdbd80, be_pcl_mutex = {__data = {__lock = 0, __count = 0, __owner = 0, __nusers = 0, __kind = 0, __spins = 0, __list = {__prev = 0x0, __next = 0x0}}, __size = '\000' <repeats 39 times>, __align = 0}, be_syncinfo = 0x0, be_pb = 0x0, be_cf_ocs = 0x5555558e7ec0, be_private = 0x5555559fa4f0, be_next = { stqe_next = 0x0}} cb = {sc_next = 0x0, sc_response = 0x555555602ff0 <over_back_response>, sc_cleanup = 0, sc_private = 0x5555559f76b0} sc = <optimized out> rc = 32768 __PRETTY_FUNCTION__ = "over_op_func" #8 0x00005555555b0f9c in fe_op_modrdn (op=0x7fffe8000930, rs=0x7ffff1106930) at modrdn.c:314 repl_user = <optimized out> dest_ndn = {bv_len = 38, bv_val = 0x7fffe80016e8 "cn=test2,ou=people,dc=my-domain,dc=com"} dest_pndn = {bv_len = 29, bv_val = 0x7fffe80016c0 "ou=people,dc=my-domain,dc=com"} pdn = {bv_len = 0, bv_val = 0x0} op_be = 0x5555559fa350 bd = 0x5555558ea2c0 diff = <optimized out> #9 0x00005555555b207e in do_modrdn (op=0x7fffe8000930, rs=0x7ffff1106930) at modrdn.c:186 dn = {bv_len = 38, bv_val = 0x7fffe81065c7 "cn=test1,ou=People,dc=my-domain,dc=com"} newrdn = {bv_len = 8, bv_val = 0x7fffe81065ef "cn=test2"} newSuperior = {bv_len = 29, bv_val = 0x7fffe81065fc "ou=People,dc=my-domain,dc=com"} deloldrdn = -1 pnewSuperior = {bv_len = 29, bv_val = 0x7fffe8001658 "ou=People,dc=my-domain,dc=com"} nnewSuperior = {bv_len = 29, bv_val = 0x7fffe80016c0 "ou=people,dc=my-domain,dc=com"} length = 29 #10 0x0000555555595d21 in connection_operation (ctx=ctx@entry=0x7ffff1106b60, arg_v=arg_v@entry=0x7fffe8000930) at connection.c:1150 rc = 80 cancel = <optimized out> op = 0x7fffe8000930 rs = {sr_type = REP_RESULT, sr_tag = 109, sr_msgid = 2, sr_err = 0, sr_matched = 0x0, sr_text = 0x0, sr_ref = 0x0, sr_ctrls = 0x0, sr_un = {sru_search = {r_entry = 0x0, r_attr_flags = 0, r_operational_attrs = 0x0, r_attrs = 0x0, r_nentries = 0, r_v2ref = 0x0}, sru_sasl = {r_sasldata = 0x0}, sru_extended = {r_rspoid = 0x0, r_rspdata = 0x0}}, sr_flags = 0} tag = 108 opidx = SLAP_OP_MODRDN conn = 0x555555a2ea00 memctx = 0x7fffe8000ed0 memctx_null = 0x0 memsiz = 1048576 __PRETTY_FUNCTION__ = "connection_operation" #11 0x0000555555596079 in connection_read_thread (ctx=0x7ffff1106b60, argv=<optimized out>) at connection.c:1286 rc = <optimized out> cri = {op = 0x7fffe8000930, func = 0, arg = 0x0, ctx = <optimized out>, nullop = <optimized out>} s = <optimized out> #12 0x00007ffff7b997f3 in ldap_int_thread_pool_wrapper (xpool=0x5555559a1b60) at tpool.c:688 pool = 0x5555559a1b60 task = 0x7fffec0008c0 work_list = <optimized out> ctx = {ltu_id = 140737237776128, ltu_key = {{ltk_key = 0x555555593ee0, ltk_data = 0x7fffe8000dc0, ltk_free = 0x555555593fb0 <conn_counter_destroy>}, {ltk_key = 0x5555555edcc0, ltk_data = 0x7fffe8000ed0, ltk_free = 0x5555555edce0 <slap_sl_mem_destroy>}, {ltk_key = 0x555555bdae00, ltk_data = 0x7fffe81010f0, ltk_free = 0x555555648bb0 <bdb_reader_free>}, {ltk_key = 0x5555555aa480, ltk_data = 0x0, ltk_free = 0x5555555aa3e0 <slap_op_q_destroy>}, {ltk_key = 0x0, ltk_data = 0x0, ltk_free = 0} <repeats 28 times>}} kctx = <optimized out> keyslot = <optimized out> hash = <optimized out> __PRETTY_FUNCTION__ = "ldap_int_thread_pool_wrapper" #13 0x00007ffff6e61d14 in start_thread (arg=0x7ffff1107700) at pthread_create.c:309 __res = <optimized out> pd = 0x7ffff1107700 now = <optimized out> unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140737237776128, 5431369951291209288, 1, 140737354125312, 140737237776128, 23, -5431349871756872120, -5431349957038737848}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = { prev = 0x0, cleanup = 0x0, canceltype = 0}}} not_first_call = 0 pagesize_m1 = <optimized out> sp = <optimized out> freesize = <optimized out> #14 0x00007ffff632a67d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 No locals. No symbol "bt" in current context. #0 rwm_op_rollback (op=op@entry=0x7fffe8000930, ros=0x7fffe8001738, rs=<optimized out>) at rwm.c:110 No locals. #1 0x00007ffff210f1c2 in rwm_op_cleanup (op=0x7fffe8000930, rs=<optimized out>) at rwm.c:165 cb = 0x7fffe8001718 ros = <optimized out> #2 0x00005555555a606b in slap_cleanup_play (op=op@entry=0x7fffe8000930, rs=rs@entry=0x7ffff1106930) at result.c:541 sc_next = 0x7ffff11065c0 sc_nextp = 0x7fffe8001718 sc = 0x7fffe8001718 scp = 0x7ffff1106018 #3 0x00005555555a6573 in send_ldap_response (op=op@entry=0x7fffe8000930, rs=rs@entry=0x7ffff1106930) at result.c:733 berbuf = {buffer = "\000\000\001\000\001\000\000\000\377\377\377\377\377\377\377\377", '\000' <repeats 24 times>, "F\030\000\350\377\177\000\000\024(\000\350\377\177\000\000\000\000\000\000\000\000\000\000F\030\000\350\377\177\000\000\320\016\000\350\377\177\000\000P\373\275UUU\000\000\200v\357\367\377\177\000\000\001\000\000\000hw\001", '\000' <repeats 17 times>"\266, \252r\367\377\177", '\000' <repeats 11 times>, "a\370<\316m]\037\200*\227\367\377\177\000\000\001\000\000\000UU\000\000\321\323vP\000\000\000\000\350\n\000\350\377\177\000\000\003", '\000' <repeats 23 times>"\225, \362\227\367\311\362\245\303\000\000\000\000\000\000\000\000+\246fUUU\000\000\030ӿUUU\000\000\223\204+\366\377\177\000\000\060\065\020\350\377\177\000\000\000a\370<\316m]\037", ialign = 65536, lalign = 4295032832, falign = 9.18354962e-41, dalign = 2.1220281700514382e-314, palign = 0x100010000 <Address 0x100010000 out of bounds>} ber = <optimized out> rc = 32768 bytes = <optimized out> __PRETTY_FUNCTION__ = "send_ldap_response" #4 0x00005555555a7126 in slap_send_ldap_result (op=0x7fffe8000930, rs=0x7ffff1106930) at result.c:860 tmp = 0x0 otext = 0x0 oref = 0x0 __PRETTY_FUNCTION__ = "slap_send_ldap_result" #5 0x0000555555621a50 in hdb_modrdn (op=0x7fffe8000930, rs=0x7ffff1106930) at modrdn.c:789 bdb = 0x5555559fa4f0 children = 0x55555599d260 entry = 0x55555599cfc0 p_dn = {bv_len = 29, bv_val = 0x7fffe8102399 "ou=People,dc=my-domain,dc=com"} p_ndn = {bv_len = 29, bv_val = 0x7fffe81023c9 ""} new_dn = {bv_len = 38, bv_val = 0x0} new_ndn = {bv_len = 38, bv_val = 0x0} e = <optimized out> p = <optimized out> ei = 0x7fffe8103f00 eip = 0x7fffe410a0a0 nei = 0x7fffe410a0a0 neip = 0x0 textbuf = "0\t\000\350\377\177\000\000\000e\020\361\377\177\000\000 i\237UUU\000\000\230\060\021\362\377\177\000\000\200\241^\366\377\177\000\000\000\000\000\000\316m]\037&\000\000\000\000\000\000\000\060\022\000\350\377\177\000\000\060\t\000\350\377\177\000\000\070\027\000\350\377\177\000\000\000\000\000\000\000\000\000\000)\323\020\362\377\177\000\000&\000\000\000\000\000\000\000\060\022\000\350\377\177\000\000&\000\000\000\000\000\000\000\270\022\000\350\377\177\000\000\000k\237UUU\000\000\000\352\242UUU\000\000\314X\021\362\377\177\000\000\060i\020\361\377\177\000\000\030\027\000\350\377\177\000\000\030\027\000\350\377\177\000\000\060i\020\361\377\177\000\000\332\326\020\362\377\177\000\000\360d\020\361\377\177\000\000\020e\020\361\377\177\000\000\b\000\000\000\000\000\000\000\270\023\000\350\377\177\000\000\b\000\000\000\000\000\000\000\350\023\000\350\377\177\000\000\000k\237UUU\000\000\000\352\242UUU\000" ltid = 0x0 lt2 = 0x7fffe81068f0 opinfo = {boi_oe = {oe_next = {sle_next = 0x0}, oe_key = 0x0}, boi_txn = 0x7fffe8106730, boi_locks = 0x0, boi_err = 0, boi_acl_cache = 0 '\000', boi_flag = 0 '\000'} dummy = {e_id = 4, e_name = {bv_len = 38, bv_val = 0x7fffe8106890 "cn=test2,ou=People,dc=my-domain,dc=com"}, e_nname = {bv_len = 38, bv_val = 0x7fffe81068c0 "cn=test2,ou=people,dc=my-domain,dc=com"}, e_attrs = 0x0, e_ocflags = 256, e_bv = {bv_len = 0, bv_val = 0x0}, e_private = 0x7fffe8103f00} np = <optimized out> np_dn = <optimized out> np_ndn = <optimized out> new_parent_dn = <optimized out> manageDSAit = 0 lock = {off = 164424, ndx = 98, gen = 2, mode = DB_LOCK_WRITE} plock = {off = 157848, ndx = 932, gen = 2, mode = DB_LOCK_READ} nplock = {off = 0, ndx = 1436511616, gen = 21845, mode = 4044383224} num_retries = 0 preread_ctrl = 0x0 postread_ctrl = 0x0 ctrls = {0x0, 0x555555a2ea00, 0x0, 0x7ffff11064a0, 0x7ffff1106480, 0x7ffff1106450} num_ctrls = 0 rc = <optimized out> parent_is_glue = 0 parent_is_leaf = 1 __PRETTY_FUNCTION__ = "hdb_modrdn" #6 0x0000555555603c96 in overlay_op_walk (op=op@entry=0x7fffe8000930, rs=0x7ffff1106930, which=op_modrdn, oi=0x5555559f76b0, on=0x0) at backover.c:671 func = <optimized out> rc = 32768 #7 0x0000555555603deb in over_op_func (op=0x7fffe8000930, rs=<optimized out>, which=<optimized out>) at backover.c:723 oi = <optimized out> on = <optimized out> be = 0x5555559fa350 db = {bd_info = 0x5555558e3620, bd_self = 0x5555559fa350, be_ctrls = "\000\001\001\001\000\001\000\000\001\000\000\001\001\000\001", '\000' <repeats 17 times>, "\001", be_flags = 2312, be_restrictops = 0, be_requires = 0, be_ssf_set = {sss_ssf = 0, sss_transport = 0, sss_tls = 0, sss_sasl = 0, sss_update_ssf = 0, sss_update_transport = 0, sss_update_tls = 0, sss_update_sasl = 0, sss_simple_bind = 0}, be_suffix = 0x555555a1df40, be_nsuffix = 0x555555a1df70, be_schemadn = {bv_len = 0, bv_val = 0x0}, be_schemandn = {bv_len = 0, bv_val = 0x0}, be_rootdn = {bv_len = 30, bv_val = 0x555555a1e010 "cn=Manager,dc=my-domain,dc=com"}, be_rootndn = {bv_len = 30, bv_val = 0x555555a1e060 "cn=manager,dc=my-domain,dc=com"}, be_rootpw = {bv_len = 6, bv_val = 0x555555a1dee0 "secret"}, be_max_deref_depth = 15, be_def_limit = {lms_t_soft = 3600, lms_t_hard = 0, lms_s_soft = 500, lms_s_hard = 0, lms_s_unchecked = -1, lms_s_pr = 0, lms_s_pr_hide = 0, lms_s_pr_total = 0}, be_limits = 0x0, be_acl = 0x0, be_dfltaccess = ACL_READ, be_extra_anlist = 0x0, be_update_ndn = {bv_len = 0, bv_val = 0x0}, be_update_refs = 0x0, be_pending_csn_list = 0x555555bdbd80, be_pcl_mutex = {__data = {__lock = 0, __count = 0, __owner = 0, __nusers = 0, __kind = 0, __spins = 0, __list = {__prev = 0x0, __next = 0x0}}, __size = '\000' <repeats 39 times>, __align = 0}, be_syncinfo = 0x0, be_pb = 0x0, be_cf_ocs = 0x5555558e7ec0, be_private = 0x5555559fa4f0, be_next = {stqe_next = 0x0}} cb = {sc_next = 0x0, sc_response = 0x555555602ff0 <over_back_response>, sc_cleanup = 0, sc_private = 0x5555559f76b0} sc = <optimized out> rc = 32768 __PRETTY_FUNCTION__ = "over_op_func" #8 0x00005555555b0f9c in fe_op_modrdn (op=0x7fffe8000930, rs=0x7ffff1106930) at modrdn.c:314 repl_user = <optimized out> dest_ndn = {bv_len = 38, bv_val = 0x7fffe80016e8 "cn=test2,ou=people,dc=my-domain,dc=com"} dest_pndn = {bv_len = 29, bv_val = 0x7fffe80016c0 "ou=people,dc=my-domain,dc=com"} pdn = {bv_len = 0, bv_val = 0x0} op_be = 0x5555559fa350 bd = 0x5555558ea2c0 diff = <optimized out> #9 0x00005555555b207e in do_modrdn (op=0x7fffe8000930, rs=0x7ffff1106930) at modrdn.c:186 dn = {bv_len = 38, bv_val = 0x7fffe81065c7 "cn=test1,ou=People,dc=my-domain,dc=com"} newrdn = {bv_len = 8, bv_val = 0x7fffe81065ef "cn=test2"} newSuperior = {bv_len = 29, bv_val = 0x7fffe81065fc "ou=People,dc=my-domain,dc=com"} deloldrdn = -1 pnewSuperior = {bv_len = 29, bv_val = 0x7fffe8001658 "ou=People,dc=my-domain,dc=com"} nnewSuperior = {bv_len = 29, bv_val = 0x7fffe80016c0 "ou=people,dc=my-domain,dc=com"} length = 29 #10 0x0000555555595d21 in connection_operation (ctx=ctx@entry=0x7ffff1106b60, arg_v=arg_v@entry=0x7fffe8000930) at connection.c:1150 rc = 80 cancel = <optimized out> op = 0x7fffe8000930 rs = {sr_type = REP_RESULT, sr_tag = 109, sr_msgid = 2, sr_err = 0, sr_matched = 0x0, sr_text = 0x0, sr_ref = 0x0, sr_ctrls = 0x0, sr_un = {sru_search = {r_entry = 0x0, r_attr_flags = 0, r_operational_attrs = 0x0, r_attrs = 0x0, r_nentries = 0, r_v2ref = 0x0}, sru_sasl = {r_sasldata = 0x0}, sru_extended = {r_rspoid = 0x0, r_rspdata = 0x0}}, sr_flags = 0} tag = 108 opidx = SLAP_OP_MODRDN conn = 0x555555a2ea00 memctx = 0x7fffe8000ed0 memctx_null = 0x0 memsiz = 1048576 __PRETTY_FUNCTION__ = "connection_operation" #11 0x0000555555596079 in connection_read_thread (ctx=0x7ffff1106b60, argv=<optimized out>) at connection.c:1286 rc = <optimized out> cri = {op = 0x7fffe8000930, func = 0, arg = 0x0, ctx = <optimized out>, nullop = <optimized out>} s = <optimized out> #12 0x00007ffff7b997f3 in ldap_int_thread_pool_wrapper (xpool=0x5555559a1b60) at tpool.c:688 pool = 0x5555559a1b60 task = 0x7fffec0008c0 work_list = <optimized out> ctx = {ltu_id = 140737237776128, ltu_key = {{ltk_key = 0x555555593ee0, ltk_data = 0x7fffe8000dc0, ltk_free = 0x555555593fb0 <conn_counter_destroy>}, {ltk_key = 0x5555555edcc0, ltk_data = 0x7fffe8000ed0, ltk_free = 0x5555555edce0 <slap_sl_mem_destroy>}, {ltk_key = 0x555555bdae00, ltk_data = 0x7fffe81010f0, ltk_free = 0x555555648bb0 <bdb_reader_free>}, {ltk_key = 0x5555555aa480, ltk_data = 0x0, ltk_free = 0x5555555aa3e0 <slap_op_q_destroy>}, {ltk_key = 0x0, ltk_data = 0x0, ltk_free = 0} <repeats 28 times>}} kctx = <optimized out> keyslot = <optimized out> hash = <optimized out> __PRETTY_FUNCTION__ = "ldap_int_thread_pool_wrapper" #13 0x00007ffff6e61d14 in start_thread (arg=0x7ffff1107700) at pthread_create.c:309 __res = <optimized out> pd = 0x7ffff1107700 now = <optimized out> unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140737237776128, 5431369951291209288, 1, 140737354125312, 140737237776128, 23, -5431349871756872120, -5431349957038737848}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}} not_first_call = 0 pagesize_m1 = <optimized out> sp = <optimized out> freesize = <optimized out> #14 0x00007ffff632a67d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 No locals. #0 0x00000000005a39de in rwm_op_rollback (op=0x7fffe4002960, rs=0x7ffff23e5a50, ros=0x7fffe4003558) at ../../../../servers/slapd/overlays/rwm.c:111 __PRETTY_FUNCTION__ = "rwm_op_rollback" #1 0x00000000005a3c79 in rwm_op_cleanup (op=0x7fffe4002960, rs=0x7ffff23e5a50) at ../../../../servers/slapd/overlays/rwm.c:167 cb = 0x7fffe4003538 ros = 0x7fffe4003558 #2 0x00000000004670e8 in slap_cleanup_play (op=0x7fffe4002960, rs=0x7ffff23e5a50) at ../../../servers/slapd/result.c:541 sc_next = 0x7ffff23e5690 sc_nextp = 0x7fffe4003538 sc = 0x7fffe4003538 scp = 0x7ffff23e5080 #3 0x0000000000467b16 in send_ldap_response (op=0x7fffe4002960, rs=0x7ffff23e5a50) at ../../../servers/slapd/result.c:733 berbuf = {buffer = "\000\000\001\000\001\000\000\000\377\377\377\377\377\377\377\377", '\000' <repeats 24 times>, "f6\000\344\377\177\000\000\064F\000\344\377\177\000\000\000\000\000\000\000\000\000\000f6\000\344\377\177\000\000\200'\000\344\377\177\000\000\017\326vP\000\000\000\000\000\017ƾ\032\372\235\264\000\000\000\000\000\000\000\000ĥ`", '\000' <repeats 13 times>, "\030+\000\344\377\177\000\000\003", '\000' <repeats 15 times>"\356, &\\\000\000\000\000\000иV\000\000\000\000\000 \314\020\344\377\177\000\000\000\017ƾ\032\372\235\264@R>\362\377\177\000\000H\314\020\344\377\177\000\000\a\000\000\000\000\000\000\000\361\264d\000\000\000\000\000\004\000\000\000\000\000\000\000P0\000\344\377\177", '\000' <repeats 18 times>, "PR>\362\377\177\000\000Pp\275\000\000\000\000", ialign = 65536, lalign = 4295032832, falign = 9.18354962e-41, dalign = 2.1220281700514382e-314, palign = 0x100010000 <Address 0x100010000 out of bounds>} ber = 0x7ffff23e50f0 rc = 32768 bytes = 14 __PRETTY_FUNCTION__ = "send_ldap_response" #4 0x0000000000468318 in slap_send_ldap_result (op=0x7fffe4002960, rs=0x7ffff23e5a50) at ../../../servers/slapd/result.c:860 tmp = 0x0 otext = 0x0 oref = 0x0 __PRETTY_FUNCTION__ = "slap_send_ldap_result" #5 0x000000000051e4a9 in hdb_modrdn (op=0x7fffe4002960, rs=0x7ffff23e5a50) at modrdn.c:789 bdb = 0x9ebd80 children = 0x9928d0 entry = 0x992630 p_dn = {bv_len = 29, bv_val = 0x7fffe410b7f9 "ou=People,dc=my-domain,dc=com"} p_ndn = {bv_len = 29, bv_val = 0x7fffe410b829 ""} new_dn = {bv_len = 38, bv_val = 0x0} new_ndn = {bv_len = 38, bv_val = 0x0} e = 0xbf3c78 p = 0x0 ei = 0x7fffe410cc20 eip = 0x7fffe410b970 nei = 0x7fffe410b970 neip = 0x0 textbuf = "X5\000\344\377\177\000\000%\231e\000\000\000\000\000PZ>\362\377\177\000\000`)\000\344\377\177\000\000\220U>\362\377\177\000\000\000\000\000\000\000\000\000\000\320{\236\000\000\000\000\000\260}\236\000\000\000\000\000&\000\000\000\000\000\000\000P0\000\344\377\177\000\000&\000\000\000\000\000\000\000\330\060\000\344\377\177\000\000\260}\236\000\000\000\000\000\200(\242\000\000\000\000\000%\231e\000\000\000\000\000PZ>\362\377\177\000\000\320U>\362\377\177\000\000BXZ\000\000\000\000\000PZ>\362\377\177\000\000`)\000\344\377\177\000\000PZ>\362\000\200\000\000\320{\236\000\000\000\000\000\260}\236\000\000\000\000\000\070\065\000\344\377\177\000\000\035\000\000\000\000\000\000\000\340\064\000\344\377\177\000\000\035\000\000\000\000\000\000\000x4\000\344\377\177\000\000\b\000\000\000\000\000\000\000\330\061\000\344\377\177\000\000\b\000\000\000\000\000\000\000\b"... textlen = 256 ltid = 0x0 lt2 = 0x7fffe410d8d0 opinfo = {boi_oe = {oe_next = {sle_next = 0x0}, oe_key = 0x0}, boi_txn = 0x7fffe40024f0, boi_locks = 0x0, boi_err = 0, boi_acl_cache = 0 '\000', boi_flag = 0 '\000'} dummy = {e_id = 4, e_name = {bv_len = 38, bv_val = 0x7fffe4002650 "cn=test2,ou=People,dc=my-domain,dc=com"}, e_nname = {bv_len = 38, bv_val = 0x7fffe4002680 "cn=test2,ou=people,dc=my-domain,dc=com"}, e_attrs = 0x0, e_ocflags = 256, e_bv = {bv_len = 0, bv_val = 0x0}, e_private = 0x7fffe410cc20} np = 0x0 np_dn = 0x0 np_ndn = 0x7ffff23e5360 new_parent_dn = 0x7ffff23e5350 manageDSAit = 0 lock = {off = 164424, ndx = 98, gen = 2, mode = DB_LOCK_WRITE} plock = {off = 157848, ndx = 932, gen = 2, mode = DB_LOCK_READ} nplock = {off = 0, ndx = 0, gen = 0, mode = DB_LOCK_NG} num_retries = 0 preread_ctrl = 0x0 postread_ctrl = 0x0 ctrls = {0x0, 0x7fffe4003050, 0xa22880, 0x0, 0x7ffff23e54a0, 0x5abe87} num_ctrls = 0 rc = 0 parent_is_glue = 0 parent_is_leaf = 1 settle = 0 __PRETTY_FUNCTION__ = "hdb_modrdn" #6 0x00000000004ebf0c in overlay_op_walk (op=0x7fffe4002960, rs=0x7ffff23e5a50, which=op_modrdn, oi=0x9e0c10, on=0x0) at ../../../servers/slapd/backover.c:671 func = 0x8bd198 rc = 32768 #7 0x00000000004ec141 in over_op_func (op=0x7fffe4002960, rs=0x7ffff23e5a50, which=op_modrdn) at ../../../servers/slapd/backover.c:723 oi = 0x9e0c10 on = 0x9e7bd0 be = 0x9ebbe0 db = {bd_info = 0x8bd140, bd_self = 0x9ebbe0, be_ctrls = "\000\001\001\001\000\001\000\000\001\000\000\001\001\000\001\001", '\000' <repeats 16 times>, "\001", be_flags = 264, be_restrictops = 0, be_requires = 0, be_ssf_set = {sss_ssf = 0, sss_transport = 0, sss_tls = 0, sss_sasl = 0, sss_update_ssf = 0, sss_update_transport = 0, sss_update_tls = 0, sss_update_sasl = 0, sss_simple_bind = 0}, be_suffix = 0x9d2740, be_nsuffix = 0x9ebbb0, be_schemadn = {bv_len = 0, bv_val = 0x0}, be_schemandn = {bv_len = 0, bv_val = 0x0}, be_rootdn = {bv_len = 30, bv_val = 0x9ec140 "cn=Manager,dc=my-domain,dc=com"}, be_rootndn = {bv_len = 30, bv_val = 0x9ec190 "cn=manager,dc=my-domain,dc=com"}, be_rootpw = {bv_len = 6, bv_val = 0x9ec440 "secret"}, be_max_deref_depth = 15, be_def_limit = {lms_t_soft = 3600, lms_t_hard = 0, lms_s_soft = 500, lms_s_hard = 0, lms_s_unchecked = -1, lms_s_pr = 0, lms_s_pr_hide = 0, lms_s_pr_total = 0}, be_limits = 0x0, be_acl = 0x0, be_dfltaccess = ACL_READ, be_extra_anlist = 0x0, be_update_ndn = {bv_len = 0, bv_val = 0x0}, be_update_refs = 0x0, be_pending_csn_list = 0xbd7030, be_pcl_mutex = {__data = {__lock = 0, __count = 0, __owner = 0, __nusers = 0, __kind = 0, __spins = 0, __list = {__prev = 0x0, __next = 0x0}}, __size = '\000' <repeats 39 times>, __align = 0}, be_syncinfo = 0x0, be_pb = 0x0, be_cf_ocs = 0x8c3400, be_private = 0x9ebd80, be_next = {stqe_next = 0x0}} cb = {sc_next = 0x0, sc_response = 0x4eacb0 <over_back_response>, sc_cleanup = 0, sc_private = 0x9e0c10} sc = 0x0 rc = 32768 __PRETTY_FUNCTION__ = "over_op_func" #8 0x00000000004ec2d8 in over_op_modrdn (op=0x7fffe4002960, rs=0x7ffff23e5a50) at ../../../servers/slapd/backover.c:768 No locals. #9 0x00000000004765fa in fe_op_modrdn (op=0x7fffe4002960, rs=0x7ffff23e5a50) at ../../../servers/slapd/modrdn.c:314 repl_user = 0 dest_ndn = {bv_len = 38, bv_val = 0x7fffe4003508 "cn=test2,ou=people,dc=my-domain,dc=com"} dest_pndn = {bv_len = 29, bv_val = 0x7fffe40034e0 "ou=people,dc=my-domain,dc=com"} pdn = {bv_len = 0, bv_val = 0x0} op_be = 0x9ebbe0 bd = 0x8c7620 diff = 0 #10 0x0000000000475d88 in do_modrdn (op=0x7fffe4002960, rs=0x7ffff23e5a50) at ../../../servers/slapd/modrdn.c:186 dn = {bv_len = 38, bv_val = 0x7fffe410cb37 "cn=test1,ou=People,dc=my-domain,dc=com"} newrdn = {bv_len = 8, bv_val = 0x7fffe410cb5f "cn=test2"} newSuperior = {bv_len = 29, bv_val = 0x7fffe410cb6c "ou=People,dc=my-domain,dc=com"} deloldrdn = -1 pnewSuperior = {bv_len = 29, bv_val = 0x7fffe4003478 "ou=People,dc=my-domain,dc=com"} nnewSuperior = {bv_len = 29, bv_val = 0x7fffe40034e0 "ou=people,dc=my-domain,dc=com"} length = 29 #11 0x000000000044fc27 in connection_operation (ctx=0x7ffff23e5b90, arg_v=0x7fffe4002960) at ../../../servers/slapd/connection.c:1150 rc = 80 cancel = 0 op = 0x7fffe4002960 rs = {sr_type = REP_RESULT, sr_tag = 109, sr_msgid = 2, sr_err = 0, sr_matched = 0x0, sr_text = 0x0, sr_ref = 0x0, sr_ctrls = 0x0, sr_un = {sru_search = {r_entry = 0x0, r_attr_flags = 0, r_operational_attrs = 0x0, r_attrs = 0x0, r_nentries = 0, r_v2ref = 0x0}, sru_sasl = {r_sasldata = 0x0}, sru_extended = {r_rspoid = 0x0, r_rspdata = 0x0}}, sr_flags = 0} tag = 108 opidx = SLAP_OP_MODRDN conn = 0xa22880 memctx = 0x7fffe4002780 memctx_null = 0x0 memsiz = 1048576 __PRETTY_FUNCTION__ = "connection_operation" #12 0x0000000000450254 in connection_read_thread (ctx=0x7ffff23e5b90, argv=0x17) at ../../../servers/slapd/connection.c:1286 rc = 0 cri = {op = 0x7fffe4002960, func = 0, arg = 0x0, ctx = 0x7ffff23e5b90, nullop = 0} s = 23 #13 0x00000000005c78ad in ldap_int_thread_pool_wrapper (xpool=0x9973b0) at ../../../libraries/libldap_r/tpool.c:688 pool = 0x9973b0 task = 0x7fffec000a20 work_list = 0x997448 ctx = {ltu_id = 140737257563904, ltu_key = {{ltk_key = 0x44f70c, ltk_data = 0x7fffe40028f0, ltk_free = 0x44f5df <conn_counter_destroy>}, {ltk_key = 0x4caa67, ltk_data = 0x7fffe4002780, ltk_free = 0x4ca88c <slap_sl_mem_destroy>}, {ltk_key = 0x46c531, ltk_data = 0x0, ltk_free = 0x46c484 <slap_op_q_destroy>}, {ltk_key = 0xbd9430, ltk_data = 0x7fffe4106590, ltk_free = 0x56eac3 <bdb_reader_free>}, {ltk_key = 0x0, ltk_data = 0x7fffe4000ac0, ltk_free = 0}, {ltk_key = 0x0, ltk_data = 0x0, ltk_free = 0} <repeats 22 times>, {ltk_key = 0x0, ltk_data = 0x7ffff6c46ba5, ltk_free = 0}, {ltk_key = 0x0, ltk_data = 0x0, ltk_free = 0}, {ltk_key = 0x0, ltk_data = 0x0, ltk_free = 0}, {ltk_key = 0x0, ltk_data = 0x0, ltk_free = 0}, {ltk_key = 0x0, ltk_data = 0x0, ltk_free = 0}}} kctx = 0x0 i = 32 keyslot = 949 hash = 3994472373 __PRETTY_FUNCTION__ = "ldap_int_thread_pool_wrapper" #14 0x00007ffff6c45d14 in start_thread (arg=0x7ffff23e6700) at pthread_create.c:309 __res = <optimized out> pd = 0x7ffff23e6700 now = <optimized out> unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140737257563904, -4915901394837331576, 1, 140737354125312, 140737257563904, 0, 4915909644372648328, 4915916705226662280}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}} not_first_call = 0 pagesize_m1 = <optimized out> sp = <optimized out> freesize = <optimized out> #15 0x00007ffff611867d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 No locals.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs