[Date Prev][Date Next]
Re: (ITS#7551) [lmdb] bugfix for mdb_cursor_put with MDB_MULTIPLE
- To: openldap-its@OpenLDAP.org
- Subject: Re: (ITS#7551) [lmdb] bugfix for mdb_cursor_put with MDB_MULTIPLE
- From: email@example.com
- Date: Sat, 23 Mar 2013 21:05:40 GMT
- Auto-submitted: auto-generated (OpenLDAP-ITS)
> Full_Name: Claude Brisson
> Version: HEAD
> OS: linux
> URL: ftp://ftp.openldap.org/incoming/0001-bugfix-for-mdb_cursor_put-with-MDB_MULTIPLE.patch
> Submission from: (NULL) (188.8.131.52)
> (once again with the attachment...)
> This patch fixes the following problem:
Thanks for the fix, applied to mdb.master.
> In mdb_cursor_put, section 'put_sub', if the variable dkey.mv_size is non-zero,
> then it means dkey contains some original data which has to be put back in the
> child db, typically when the child db has just been created.
> But when using MDB_MULTIPLE, if this variable has not been resetted to zero, we
> may come back to this section and wrongly think that there is some original data
> to be taken care of.
> Notice: I, Claude Brisson, hereby place the following modifications to OpenLDAP
> Software (and only these modifications) into the public domain. Hence, these
> modifications may be freely used and/or redistributed for any purpose with or
> without attribution and/or other notice.
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/