openldap-bugs June 2013

openldap-bugs@openldap.org

19 participants
65 discussions

Re: (ITS#7615) NetBSD sem_open limited to 14 characters
by hyc＠symas.com 03 Jun '13

03 Jun '13

Greg(a)Akua.com wrote: > Full_Name: Greg Kerr > Version: 2.4.35 > OS: NetBSD & FreeBSD > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (50.88.130.68) > > > MDB is not usable on NetBSD because mdb.c has > > sprintf(env->me_txns->mti_wmname, "/MDBw%s", hexbuf); > > To create the semaphore name. > > This results in a 21 character name which is beyond the 14 allowed per "man > sem_open" That's unfortunate. In Linux this limit is 251 characters. Seems you'd need to use the btoa algorithm to safely fit a hash into this size limit. Pretty sure we've tested successfully on FreeBSD and MacOSX already, so apparently they don't suffer from this same limit. > "less than 14 characters in length not including the terminating null > character." > > I will make a local patch ... and maybe it's a NetBSD bug - or at least the > package maintainers ... I will report to him. > > At any rate, the failure of mdb with result code 63 (name too long) was very > confusing ... better error reporting in this file would be nice. > > -- -- 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#7614) Markup error in slapd.conf.5
by hyc＠symas.com 03 Jun '13

03 Jun '13

esr(a)thyrsus.com wrote: > Full_Name: Eric S. Raymond > Version: > OS: Linux > URL: http://www.catb.org/~esr/doclifter/prepatch/slapd.conf.5.patch > Submission from: (NULL) (2001:470:e34c:0:226:18ff:fea6:dca4) > > > List syntax error. This means .IP, .TP or .RS/.RE markup is garbled. > Common causes include .TP just before a section header, .TP entries > with tags but no bodies, and mandoc lists with no trailing .El. > These confuse doclifter, and may also mess up stricter man-page > browsers like Xman and Rosetta. > > Fix patch at link. The patch changes much more than your bug report mentions. The error message you provide is pretty ambiguous, in particular you haven't mentioned exactly which markup element is out of order. Without this information we can't confirm what you're fixing. -- -- 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#7615) NetBSD sem_open limited to 14 characters
by Greg＠Akua.com 03 Jun '13

03 Jun '13

Full_Name: Greg Kerr Version: 2.4.35 OS: NetBSD & FreeBSD URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (50.88.130.68) MDB is not usable on NetBSD because mdb.c has sprintf(env->me_txns->mti_wmname, "/MDBw%s", hexbuf); To create the semaphore name. This results in a 21 character name which is beyond the 14 allowed per "man sem_open" "less than 14 characters in length not including the terminating null character." I will make a local patch ... and maybe it's a NetBSD bug - or at least the package maintainers ... I will report to him. At any rate, the failure of mdb with result code 63 (name too long) was very confusing ... better error reporting in this file would be nice.

1 0

(ITS#7614) Markup error in slapd.conf.5
by esr＠thyrsus.com 02 Jun '13

02 Jun '13

Full_Name: Eric S. Raymond Version: OS: Linux URL: http://www.catb.org/~esr/doclifter/prepatch/slapd.conf.5.patch Submission from: (NULL) (2001:470:e34c:0:226:18ff:fea6:dca4) List syntax error. This means .IP, .TP or .RS/.RE markup is garbled. Common causes include .TP just before a section header, .TP entries with tags but no bodies, and mandoc lists with no trailing .El. These confuse doclifter, and may also mess up stricter man-page browsers like Xman and Rosetta. Fix patch at link.

1 0

Re: (ITS#7594) incomplete MDB subdb cursor cleanup
by h.b.furuseth＠usit.uio.no 02 Jun '13

02 Jun '13

Howard Chu writes: >h.b.furuseth(a)usit.uio.no wrote: >> If a cursor is at a clean subDB page, and its current item is deleted >> by another cursor, then MDB_GET_CURRENT returns the deleted item. > > Fixed now in mdb.master. The subcursor on the clean page will be invalidated > when the page is touched. MDB_NEXT/MDB_PREV crash on assert(mc->mc_flags & C_INITIALIZED) since commit e31c7d3b31d8d5073195e31b283e8ccb46bd13cf, with the patch below to the test program. One partial fix: Instead return a new error code MDB_BAD_CURSOR or maybe MDB_UNSPECIFIED. Also make mdb_cursor_<next/prev>() less forgiving of errors, otherwise the user gets different success results for the two cursors again. Branch mdb/its7594 in <http://folk.uio.no/hbf/OpenLDAP/openldap.git> does this. I did not look at how to get the cursors return the same result. mdb.master output with patched test program: With clean page: Name: Key -> Data (mv_data[mv_len]): m2: a[2] -> x[2] mc/del: a[2] -> [0] a.out: mdb.c:4386: mdb_cursor_next: Assertion `mc->mc_flags & 0x01' failed. Branch mdb/its7594 output: With clean page: Name: Key -> Data (mv_data[mv_len]): m2: a[2] -> x[2] mc/del: a[2] -> [0] its7594a.c:48: mdb_cursor_get(m2, &key, &data, MDB_NEXT): MDB_BAD_CURSOR: Cursor is unusable That assert is OK since it's the test program asserting success. --- its7594.c +++ its7594a.c @@ -28,4 +28,6 @@ E(mdb_cursor_put(mc, STR2VAL("a"), STR2VAL("x"), 0)); E(mdb_cursor_put(mc, STR2VAL("a"), STR2VAL("y"), 0)); + E(mdb_cursor_put(mc, STR2VAL("b"), STR2VAL("z"), 0)); + E(mdb_cursor_put(mc, STR2VAL("c"), STR2VAL("w"), 0)); if (argc < 2) { @@ -42,8 +44,8 @@ E(mdb_cursor_del(mc, 0)); - E(mdb_cursor_get(m2, &key, &data, MDB_GET_CURRENT)); - SHOW("m2/del"); /* Should output the same as... */ - E(mdb_cursor_get(mc, &key, &data, MDB_GET_CURRENT)); - SHOW("mc/del"); /* ...this: "a[2] -> [0]". */ + E(mdb_cursor_get(mc, &key, &data, MDB_NEXT)); + SHOW("mc/del"); /* Outputs "a[2] -> [0]"... */ + E(mdb_cursor_get(m2, &key, &data, MDB_NEXT)); + SHOW("m2/del"); /* ...and this should output the same. */ mdb_txn_abort(txn); -- Hallvard

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs June 2013