Issue 4112 - back-mdb: component match indexing is broken
Summary: back-mdb: component match indexing is broken
Status: UNCONFIRMED
Alias: None
Product: OpenLDAP
Classification: Unclassified
Component: backends (show other issues)
Version: 2.3
Hardware: All All
: --- normal
Target Milestone: ---
Assignee: OpenLDAP project
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-26 08:31 UTC by Howard Chu
Modified: 2020-03-19 16:51 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Howard Chu 2005-10-26 08:31:45 UTC 
Full_Name: Howard Chu
Version: 2.3
OS: Linux
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (24.126.120.178)
Submitted by: hyc


The back-bdb component match indexing code stores per-attribute state
information in the AttrInfo structures. These structures are supposed to be
read-only; they are shared by all threads running in the backend. If two entries
are being added at once and component indices are in use they will collide here.
This code cannot be used.
Comment 1 Howard Chu 2005-11-02 23:54:44 UTC 
moved from Incoming to Development
Comment 2 ando@openldap.org 2007-08-11 07:54:31 UTC 
changed notes
Comment 3 OpenLDAP project 2014-08-01 21:04:58 UTC 
compmatch
Comment 4 Quanah Gibson-Mount 2020-03-18 20:11:58 UTC 
Does this issue exist in back-mdb?

If not, I think this should be closed as back-bdb is removed for 2.5+
Comment 5 Howard Chu 2020-03-18 20:34:50 UTC 
(In reply to Quanah Gibson-Mount from comment #4)
> Does this issue exist in back-mdb?
> 
> If not, I think this should be closed as back-bdb is removed for 2.5+

The code was copy/pasted into back-mdb and also left #if'd out. So yes, the
same issue remains unfixed, and will remain so until someone who cares about
component matching comes along to fix it.