openldap-bugs

openldap-bugs@openldap.org

1 participants
20967 discussions

Re: (ITS#8167) The new non-blocking TLS connect does not work in a reference/referral
by ondra＠mistotebe.net 14 Jun '19

14 Jun '19

On Wed, Jun 10, 2015 at 12:39:19AM +0000, ipuleston(a)SonicWALL.com wrote: > I've now uploaded the patch to the ftp.openldap.org FTP server as "ian-pule= > ston-15069.patch". Hi Ian, thank you for your work, the patch has been pushed to master (46c93e41f43da7f16270179c6eff75e450617329) and will also be part (a8cf2fb10047794c83873f5ff5c125ecd0e53168) of the upcoming 2.4.48 release. Thanks, -- Ondřej Kuzník Senior Software Engineer Symas Corporation http://www.symas.com Packaged, certified, and supported LDAP solutions powered by OpenLDAP

1 0

Re: (ITS#8450) race condition in ldap_int_utils_init
by ondra＠mistotebe.net 14 Jun '19

14 Jun '19

On Fri, Jun 24, 2016 at 08:04:27PM +0000, doug.leavitt(a)oracle.com wrote: > There is a race condition in ldap_int_utils_init that can be triggered when > multiple threads enter ldap_int_utils_init from ldap_init_initialize about the > same time. The done flag gets set immediately, before the various mutexes are > initialized. If thread A sets done, and thread B tests for done==1 before thread > A has completed the mutex inits, thread B can attempt to use an uninitialized > mutex and fail/core dump etc. > > Additionally if judt the done=1 is moved to the bottom of the function thwo > threads can both be initializing the same mutexes multiple times causes other > mayhem. > > The short term workaround for Solaris (THR APIs) is to move setting of done=1 to > after the mutex inits, and to protect the mutex inits using another statically > initialized mutex within ldap_int_utils_init. Hi Doug, a patch addressing this and ITS#7996 has been pushed to master (db40120a276c3b7968552e253aea24860fad5f60) and will also be part (cde56fad154fcd25e351c3cd84d8173d263b0a01) of the upcoming 2.4.48 release. Thanks, -- Ondřej Kuzník Senior Software Engineer Symas Corporation http://www.symas.com Packaged, certified, and supported LDAP solutions powered by OpenLDAP

1 0

Re: (ITS#7996) Global initialisation race in ldap_int_initialize
by ondra＠mistotebe.net 14 Jun '19

14 Jun '19

On Fri, Sep 08, 2017 at 02:07:19PM +0000, quanah(a)symas.com wrote: > --On Friday, September 08, 2017 1:02 PM +0000 a.cudbardb(a)freeradius.org > wrote: >>> Thanks for the report and sorry for the delay on getting to this >>> issue. I would note that for the fix to be included in the OpenLDAP >>> project, we need an IPR statement, as noted at >>> <https://www.openldap.org/devel/contributing.html>. If you can >>> provide that, and (if possible) submit the patch as git format-patch >>> via the project FTP server (include the URL in your email), then I >>> can pull it in. >> >> IPR statement is not a problem, but I don't have the original diff to = >> work from. If you can send me a copy of the FTP submission I can = >> reformat it and resubmit it. > > Hi Arran, > > The diff is in your github issues tracker. ;) > > <https://github.com/arr2036/ldapperf/issues/2#issuecomment-66242732> Hi Arran, thank you for your work, a patch addressing this has been pushed to master (db40120a276c3b7968552e253aea24860fad5f60) and will also be part (cde56fad154fcd25e351c3cd84d8173d263b0a01) of the upcoming 2.4.48 release. Thanks, -- Ondřej Kuzník Senior Software Engineer Symas Corporation http://www.symas.com Packaged, certified, and supported LDAP solutions powered by OpenLDAP

1 0

Re: (ITS#7042) [PATCH] allow unsetting of tls_* options for syncrepl
by ondra＠mistotebe.net 14 Jun '19

14 Jun '19

On Sat, Oct 21, 2017 at 03:50:48PM +0000, patrick(a)monnerat.net wrote: > Hi Quanah, > Thanks for your directives and future action. Hi Patrick, thank you for your patch, it has now been pushed to master (0f9afae02d9425e54f070ecd5ea8b954115e092b) and will also be part (e5f945bab40482e2045fede3fbe9a04210808a93) of the upcoming 2.4.48 release. Thanks, -- Ondřej Kuzník Senior Software Engineer Symas Corporation http://www.symas.com Packaged, certified, and supported LDAP solutions powered by OpenLDAP

1 0

Re: (ITS#9034) LDMB: 0.9.22/3: initial mdb_env_set_mapsize() is problematic
by hyc＠symas.com 13 Jun '19

13 Jun '19

steffen(a)sdaoden.eu wrote: > Full_Name: Steffen Nurpmeso > Version: 0.9.23 > OS: Linux > URL: https://ftp.sdaoden.eu/lmdb-bogo.tar.xz > Submission from: (NULL) (109.40.130.211) > > > A follow-up to private communication with Quanah Gibson-Mount. > You can find more in the tarball linked below. The code works as designed. No changes to mapsize handling were made between 0.9.22 and 0.9.23. Closing this ITS. -- -- 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#9036) LDMB: 0.9.23: mdb_env_info() does not report latest mapsize() after transaction abort
by hyc＠symas.com 13 Jun '19

13 Jun '19

steffen(a)sdaoden.eu wrote: > Full_Name: Steffen Nurpmeso > Version: 0.9.23 > OS: Linux > URL: https://ftp.sdaoden.eu/lmdb-bogo.tar.xz > Submission from: (NULL) (109.40.130.211) > > > A follow-up to private communication with Quanah Gibson-Mount. > You can find more in the tarball linked below > > Your README states that the behavior in LMDB 0.9.23 is different than in 0.9.22 but that is incorrect. No changes to set_mapsize() behavior were made between 0.9.22 and 0.9.23. Closing this ITS. -- -- 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#9035) LDMB: 0.9.23: mdb_env_set_maxreaders() not honoured?
by hyc＠symas.com 13 Jun '19

13 Jun '19

steffen(a)sdaoden.eu wrote: > Full_Name: Steffen Nurpmeso > Version: 0.9.23 > OS: Linux > URL: https://ftp.sdaoden.eu/lmdb-bogo.tar.xz > Submission from: (NULL) (109.40.130.211) > > > A follow-up to private communication with Quanah Gibson-Mount. > You can find more in the tarball linked below The maxreaders setting doesn't persist after all processes have closed the environment. Therefore it returns to its default value when the next process opens the environment. The code works as designed. There is no bug here. Closing this ITS. -- -- 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#9036) LDMB: 0.9.23: mdb_env_info() does not report latest mapsize() after transaction abort
by steffen＠sdaoden.eu 13 Jun '19

13 Jun '19

Full_Name: Steffen Nurpmeso Version: 0.9.23 OS: Linux URL: https://ftp.sdaoden.eu/lmdb-bogo.tar.xz Submission from: (NULL) (109.40.130.211) A follow-up to private communication with Quanah Gibson-Mount. You can find more in the tarball linked below

1 0

(ITS#9035) LDMB: 0.9.23: mdb_env_set_maxreaders() not honoured?
by steffen＠sdaoden.eu 13 Jun '19

13 Jun '19

1 0

(ITS#9034) LDMB: 0.9.22/3: initial mdb_env_set_mapsize() is problematic
by steffen＠sdaoden.eu 13 Jun '19

13 Jun '19

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