openldap-bugs

openldap-bugs@openldap.org

1 participants
21001 discussions

Re: (ITS#5526) Another segmentation fault
by hyc＠symas.com 23 May '08

23 May '08

quanah(a)zimbra.com wrote: > --On Friday, May 23, 2008 9:02 AM +0000 zulcss(a)ubuntu.com wrote: > >> Full_Name: Chuck Short >> Version: 3.2.7 >> OS: Ubuntu >> URL: ftp://ftp.openldap.org/incoming/ >> Submission from: (NULL) (82.142.121.161) >> >> >> Hello, >> >> We received another report of a segmentation fault in openldap 3.2.7. The >> bug report with the test case can be found at: >> >> http://bugs.launchpad.net/bugs/234196 >> >> If you have any questions please let me know. > > Sure. What is OpenLDAP 3.2.7? And the bug reported here was already fixed > in OpenLDAP 2.4.9 IIRC. Please validate bugs against 2.4.9 before filing > an ITS. Actually no, this particular bug was still present in 2.4.9. A patch is in HEAD and still needs testing. Some of the other recently filed ones were already fixed though. -- -- 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#5526) Another segmentation fault
by quanah＠zimbra.com 23 May '08

23 May '08

--On Friday, May 23, 2008 8:09 AM -0700 Quanah Gibson-Mount <quanah(a)zimbra.com> wrote: > --On Friday, May 23, 2008 9:02 AM +0000 zulcss(a)ubuntu.com wrote: > >> Full_Name: Chuck Short >> Version: 3.2.7 >> OS: Ubuntu >> URL: ftp://ftp.openldap.org/incoming/ >> Submission from: (NULL) (82.142.121.161) >> >> >> Hello, >> >> We received another report of a segmentation fault in openldap 3.2.7. The >> bug report with the test case can be found at: >> >> http://bugs.launchpad.net/bugs/234196 >> >> If you have any questions please let me know. > > Sure. What is OpenLDAP 3.2.7? And the bug reported here was already > fixed in OpenLDAP 2.4.9 IIRC. Please validate bugs against 2.4.9 before > filing an ITS. Okay, ignore me. I was thinking of a different assertion failure fixed by 2.4.9. :P But 3.2.7 still is not a valid OpenLDAP release. ;) --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: (ITS#5526) Another segmentation fault
by quanah＠zimbra.com 23 May '08

23 May '08

--On Friday, May 23, 2008 9:02 AM +0000 zulcss(a)ubuntu.com wrote: > Full_Name: Chuck Short > Version: 3.2.7 > OS: Ubuntu > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (82.142.121.161) > > > Hello, > > We received another report of a segmentation fault in openldap 3.2.7. The > bug report with the test case can be found at: > > http://bugs.launchpad.net/bugs/234196 > > If you have any questions please let me know. Sure. What is OpenLDAP 3.2.7? And the bug reported here was already fixed in OpenLDAP 2.4.9 IIRC. Please validate bugs against 2.4.9 before filing an ITS. Thanks, Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: (ITS#5506) syncprov crash with RE24 CVS
by hyc＠symas.com 23 May '08

23 May '08

Mark Cave-Ayland wrote: > Mark Cave-Ayland wrote: > >> Okay. I've arranged for a set of new packages (based upon HEAD) to be >> built and installed tomorrow, so will feedback on progress in a few days >> after the new packages have had time to settle in. > > Just to feedback on this bug: we have been running packages from CVS > HEAD dated 2008-05-14 on our client setup (which is basically openldap > 2.4.9 plus fixes for ITS#5503 and ITS#5506), and I am pleased to report > that we have had no more core files produced since the packages were > installed in the middle of last week. > > I'm happy for this ticket to be closed, plus I would suggest closing > ITS#5501, which since it hasn't occurred since, is likely to be another > symptom of this bug. Thanks for the followup. We'll close this and #5501 with 2.4.10. -- -- 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#5506) syncprov crash with RE24 CVS
by mark.cave-ayland＠siriusit.co.uk 23 May '08

23 May '08

Mark Cave-Ayland wrote: > Okay. I've arranged for a set of new packages (based upon HEAD) to be > built and installed tomorrow, so will feedback on progress in a few days > after the new packages have had time to settle in. Just to feedback on this bug: we have been running packages from CVS HEAD dated 2008-05-14 on our client setup (which is basically openldap 2.4.9 plus fixes for ITS#5503 and ITS#5506), and I am pleased to report that we have had no more core files produced since the packages were installed in the middle of last week. I'm happy for this ticket to be closed, plus I would suggest closing ITS#5501, which since it hasn't occurred since, is likely to be another symptom of this bug. Thanks once again for your help, Mark. -- Mark Cave-Ayland Sirius Corporation - The Open Source Experts http://www.siriusit.co.uk T: +44 870 608 0063

1 0

(ITS#5527) Segmentation fault in dynlist.c
by zulcss＠ubuntu.com 23 May '08

23 May '08

Full_Name: Chuck Short Version: 3.2.7 OS: Ubuntu URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (82.142.121.161) Hello, We have recieved a bug report about a segmentation fault using dynlist. You can find the bug report at: http://bugs.launchpad.net/bugs/218734 If you have any questions please feel free to ask. Thanks chuck

1 0

(ITS#5526) Another segmentation fault
by zulcss＠ubuntu.com 23 May '08

23 May '08

Full_Name: Chuck Short Version: 3.2.7 OS: Ubuntu URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (82.142.121.161) Hello, We recieved another report of a segmentation fault in openldap 3.2.7. The bug report with the test case can be found at: http://bugs.launchpad.net/bugs/234196 If you have any questions please let me know. Thanks chuck

1 0

Re: (ITS#5518) Assertion error in io.c:234: ber_flush2
by hyc＠symas.com 23 May '08

23 May '08

Howard Chu wrote: > paul(a)mad-scientist.us wrote: >> Hi all; I just posted a new bug 5525 that describes exactly how this >> happens and where the bug is. I came to this conclusion while trying to >> find a crasher in Evolution Exchange: I ran it under valgrind to find >> the use of freed memory. >> >> Hopefully this will provide us with a quick fix! > > Thanks for tracking this down Paul. I think you've nailed it for us, we should > be able to patch this pretty soon. > I replied to #5525 that a patch for this is now in HEAD. Please test. I've now closed #5525 as a dup of this bug. -- -- 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#5429) component Matching
by hyc＠symas.com 23 May '08

23 May '08

ron(a)zytrax.com wrote: > Full_Name: Ron Aitchison > Version: 2.4.8 > OS: FreeBSD (5.4/6.2) > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (209.148.181.131) > > > Component matching (RFC 3687) is defined to be released with 2.4.8. However it > is conditionally compiled from the variable LDAP_COMP_MATCH which is only set > (in servers/slapd/slap.h) if LDAP_DEVEL is set. LDAP_DEVEL is not set by default > in a normal build. The net result is that component matching is not included in > an OpenLDAP build. It's not clear that this feature is safe for use. It's certain that indexing for component matching in back-bdb is broken. Unindexed matching may or may not work. The lead developer on this feature is gone, so until someone else comes along to adopt the code it's going to remain DEVEL-only. -- -- 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#5525) libldap causes a core dump due to accessing freed memory
by hyc＠symas.com 23 May '08

23 May '08

paul(a)mad-scientist.us wrote: > Full_Name: Paul Smith > Version: 2.4.7 > OS: Ubuntu 8.04 > URL: > Submission from: (NULL) (65.78.30.67) > If you check ldap_free_connection() you'll see that it removes the LDAPConn > pointer "lc" from the list of connections before it is freed. > > BUT! The ldap_free_connection() function never does anything with the > ld->ld_defconn pointer, so if the connection we just freed is the one pointed to > by ld->ld_defconn, it is now pointing to freed memory. And that causes the > problem detected above by valgrind, or causing an assert later on: accessing > freed memory. > > I'm not really sure what the right thing to do here is, or I'd provide a patch. > Should we set ld_defconn to NULL? Is that ever a valid state? Or should we > just pick another connection from the list (and what if there isn't one?) A fix is now in HEAD, please test. The solution sets ld_defconn to NULL, and also closes ld->ld_sb if necessary. In that case, ldap_send_initial_request will create a new defconn before calling ldap_send_server_request. -- -- 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs